Triple
T1976994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piet Mondrian |
E42936
|
entity |
| Predicate | changedName |
P65
|
FINISHED |
| Object | Pieter Cornelis Mondriaan to Piet Mondrian |
—
|
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: Pieter Cornelis Mondriaan to Piet Mondrian | Statement: [Piet Mondrian, changedName, Pieter Cornelis Mondriaan to Piet Mondrian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedName Context triple: [Piet Mondrian, changedName, Pieter Cornelis Mondriaan to Piet Mondrian]
-
A.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
-
B.
nameChangeApprovedBy
Indicates that an official approval has been granted by a specific authority or party for a change of name.
-
C.
hasSubsequentNameChange
Indicates that an entity undergoes a later change to its name, resulting in a new official designation after the original.
-
D.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
-
E.
nameChangeDate
Indicates the date on which an entity’s name was officially changed.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f9a87c8190816db3888787ad76 |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff9a09c8190a81fa13f4b85bc79 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.