Triple
T8575696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osceola |
E203042
|
entity |
| Predicate | hasHeadSeparatedAfterDeath |
P83717
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Osceola, hasHeadSeparatedAfterDeath, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHeadSeparatedAfterDeath Context triple: [Osceola, hasHeadSeparatedAfterDeath, true]
-
A.
diedAfter
Indicates that one entity’s death occurred later in time than another entity’s death.
-
B.
hasMannerOfDeath
Indicates the specific way or circumstances in which an entity died, such as natural causes, accident, homicide, or suicide.
-
C.
afterDeath
Indicates that one event, state, or condition occurs subsequent to and as a result of an entity’s death.
-
D.
releasedAfterDeathOf
Indicates that something (such as a work, product, or announcement) was released only after the death of a specified person.
-
E.
containsDeathOf
Indicates that the subject includes, depicts, or involves the death of the referenced entity.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea9638c081909a537cc44e485bee |
completed | March 31, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:21 p.m.