Triple
T20960550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Lendl |
E516229
|
entity |
| Predicate | citizenshipAcquiredYear |
P11301
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Ivan Lendl, citizenshipAcquiredYear, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: citizenshipAcquiredYear Context triple: [Ivan Lendl, citizenshipAcquiredYear, 1992]
-
A.
citizenshipGrantedYear
chosen
Indicates the specific year in which an entity was officially granted citizenship.
-
B.
dateOfCitizenshipChange
Indicates the date on which an entity’s citizenship status was changed from one nationality to another.
-
C.
citizenshipDuringLifetime
Indicates that an entity held citizenship in a particular country or political unit at some point during its lifetime.
-
D.
yearOfImmigration
Indicates the specific year in which an entity immigrated to a new country or region.
-
E.
hasAncestralCitizenshipOf
Indicates that an entity holds or is recognized as holding citizenship of another entity based on ancestral or lineage connections rather than solely on birth or residence.
- 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_69e0b4fde6c48190af1398e7e734629e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6f134081908b1ed48ce708f3d5 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:31 p.m.