Triple
T31289467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAFKAP |
E797893
|
entity |
| Predicate | refersToPersonDeathDate |
P20
|
FINISHED |
| Object | 2016-04-21 |
—
|
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: 2016-04-21 | Statement: [TAFKAP, refersToPersonDeathDate, 2016-04-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToPersonDeathDate Context triple: [TAFKAP, refersToPersonDeathDate, 2016-04-21]
-
A.
dateOfDeath
chosen
Indicates the specific date on which an individual or entity died.
-
B.
dateOfDeathPrecision
Indicates the level of exactness or specificity with which an entity’s date of death is known or recorded.
-
C.
estimatedDateOfDeath
Indicates the date on which an entity is believed or calculated to have died, rather than a precisely known death date.
-
D.
namedAfterDateOfDeath
Indicates that something is named after an entity specifically using the date on which that entity died.
-
E.
deathDateEvent
Indicates the date on which a death occurred or a death-related event took place.
- 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_69f224dfde288190af313f3c221c857e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 29, 2026, 9:14 p.m.