Triple
T13367798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aka-Bo language |
E318984
|
entity |
| Predicate | languageDeathCause |
P109647
|
FINISHED |
| Object | language shift to Hindi |
—
|
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: language shift to Hindi | Statement: [Aka-Bo language, languageDeathCause, language shift to Hindi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageDeathCause Context triple: [Aka-Bo language, languageDeathCause, language shift to Hindi]
-
A.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
B.
reasonForDeath
Indicates the cause, circumstance, or condition that led to an entity’s death.
-
C.
reasonForDemise
Indicates the cause, circumstance, or factor that led to an entity’s death or termination.
-
D.
legendaryCauseOfDeath
Indicates a legendary or mythic account of how an entity died, as opposed to a historically verified cause of death.
-
E.
endOfReignReason
Indicates the cause or circumstance that led to the termination of a ruler’s reign.
- 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_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. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:32 p.m.