Triple
T13367852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bo language |
E318985
|
entity |
| Predicate | deathOfLastSpeakerEffect |
P27814
|
FINISHED |
| Object | causedLanguageExtinction |
—
|
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: causedLanguageExtinction | Statement: [Bo language, deathOfLastSpeakerEffect, causedLanguageExtinction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathOfLastSpeakerEffect Context triple: [Bo language, deathOfLastSpeakerEffect, causedLanguageExtinction]
-
A.
deathEpisode
Indicates the episode or event in which an entity’s death occurs or is depicted.
-
B.
effectOfDeath
chosen
Indicates the causal impact or consequences that a death has on another entity, state, or process.
-
C.
deathAnnouncedBy
Indicates that the occurrence of a death is publicly communicated or formally reported by a specific agent or source.
-
D.
deathIsWitnessedBy
Indicates that the occurrence of a death is directly observed or witnessed by another entity.
-
E.
deathSceneWork
Indicates that a creative work features or depicts the scene in which a character dies.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd652d48190a782fd1f57f34b6a |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.