Triple
T27599466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lauban |
E699995
|
entity |
| Predicate | postWarRenaming |
P123285
|
FINISHED |
| Object | renamed to Lubań |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: renamed to Lubań | Statement: [Lauban, postWarRenaming, renamed to Lubań]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postWarRenaming Context triple: [Lauban, postWarRenaming, renamed to Lubań]
-
A.
postWorldWarIIRenamedAs
Indicates that an entity was given a new name after the end of World War II.
-
B.
postwarRedesignationOf
chosen
Indicates the relationship in which an entity receives a new designation or identity as a result of postwar changes or reorganization.
-
C.
postWarOrder
Indicates the arrangement of political, economic, and social relations established among actors after a war has ended.
-
D.
postwarModification
Indicates that an entity has been altered, upgraded, or otherwise modified after the conclusion of a war or major conflict.
-
E.
postWarFunction
Indicates how something operated, was used, or what role it served in the period following a war.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 2:07 p.m.