Triple
T27534896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World War I veterans |
E695069
|
entity |
| Predicate | lastKnownSurvivorDiedIn |
P162483
|
FINISHED |
| Object | 21st century |
—
|
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: 21st century | Statement: [World War I veterans, lastKnownSurvivorDiedIn, 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastKnownSurvivorDiedIn Context triple: [World War I veterans, lastKnownSurvivorDiedIn, 21st century]
-
A.
lastHolderDiedIn
Indicates that the most recent holder or possessor of something died in the specified place or during the specified event or time period.
-
B.
lastInmateDeath
Indicates the date or event of the most recent death of an inmate within a given facility, system, or context.
-
C.
isSurvivorOf
Indicates that one entity has lived through, endured, or remained alive after a particular event, condition, or harmful circumstance involving another entity.
-
D.
diedShortlyBefore
Indicates that one entity’s death occurred a brief time before another specified event or entity’s death.
-
E.
discoveredAsDeadBy
Indicates that one entity was found to be dead by another entity, who discovered their deceased state.
- F. None of above. chosen
Provenance (4 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_69ef538608b081908b9f659bb09d5e0f |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f5996508190894a769a5199945d |
completed | May 2, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:28 p.m.