Triple
T37425432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tah-gah-jute |
E929974
|
entity |
| Predicate | familyKilledIn |
P193229
|
FINISHED |
| Object | Yellow Creek massacre |
—
|
NE NERFINISHED |
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: Yellow Creek massacre | Statement: [Tah-gah-jute, familyKilledIn, Yellow Creek massacre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyKilledIn Context triple: [Tah-gah-jute, familyKilledIn, Yellow Creek massacre]
-
A.
killedFamilyOf
Indicates that one entity caused the death of one or more members of another entity’s family.
-
B.
brothersKilledBy
Indicates that the referenced individuals are brothers who were killed by the same agent or in the same event.
-
C.
childrenKilledBy
Indicates that the children of a given entity were killed by another specified entity or agent.
-
D.
sonsKilledBy
Indicates that the referenced sons are those who were killed by the specified agent or entity.
-
E.
childrenKilledDuring
Indicates that one or more children were killed in the course of a specified event, action, or time period.
- 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_69f76ebf0f288190ba198a78341613b8 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
| PDg | Predicate description generation | batch_69fd3a6905b88190ae12b43576f4cc63 |
completed | May 8, 2026, 1:20 a.m. |
Created at: May 3, 2026, 4:16 p.m.