Triple
T23396404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wichita language |
E559370
|
entity |
| Predicate | lastSpeakerDied |
P56181
|
FINISHED |
| Object | 2016 |
—
|
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 | Statement: [Wichita language, lastSpeakerDied, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastSpeakerDied Context triple: [Wichita language, lastSpeakerDied, 2016]
-
A.
lastKnownSpeaker
Indicates the entity that was most recently identified or recorded as speaking in a given context or interaction.
-
B.
lastHolderDiedIn
Indicates that the most recent holder or possessor of something died in the specified place or during the specified event or time period.
-
C.
lastKnownSpeakers
chosen
Indicates the people or entities most recently known to use or speak a particular language.
-
D.
diedShortlyBefore
Indicates that one entity’s death occurred a brief time before another specified event or entity’s death.
-
E.
diedAfter
Indicates that one entity’s death occurred later in time than another entity’s death.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4dc48008190bdcf92f8d9a5232d |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:36 p.m.