Triple
T6183388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zara |
E137996
|
entity |
| Predicate | nameChangeContext |
P39961
|
FINISHED |
| Object | post-World War II |
—
|
LITERAL FINISHED |
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: post-World War II | Statement: [Zara, nameChangeContext, post-World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameChangeContext Context triple: [Zara, nameChangeContext, post-World War II]
-
A.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
-
B.
nameChangeEvent
Indicates an event in which an entity’s name is changed from one value to another.
-
C.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
D.
changedNameIn
chosen
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
-
E.
changedSurnameFrom
Indicates that an entity has adopted a new surname that was previously a different, specified surname.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06100c2b0819097f287e86f63d590 |
completed | March 22, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.