Triple
T35720707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilly Kane |
E1032461
|
entity |
| Predicate | dateOfDeathInUniverse |
P94074
|
FINISHED |
| Object | October 3, 2003 |
—
|
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: October 3, 2003 | Statement: [Lilly Kane, dateOfDeathInUniverse, October 3, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfDeathInUniverse Context triple: [Lilly Kane, dateOfDeathInUniverse, October 3, 2003]
-
A.
dateOfDeath
Indicates the specific date on which an individual or entity died.
-
B.
estimatedDateOfDeath
Indicates the date on which an entity is believed or calculated to have died, rather than a precisely known death date.
-
C.
fictionalDeathDate
chosen
Indicates the date on which a fictional character is depicted as having died within its narrative or canon.
-
D.
dateOfDeathInAH
Indicates the date on which an entity died, expressed according to the Anno Hegirae (AH) calendar system.
-
E.
dateOfPassage
Indicates the specific calendar date on which a law, bill, or formal measure was officially approved or enacted.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:05 p.m.