Triple
T22586682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nacogdoche |
E564814
|
entity |
| Predicate | positionInLegend |
P134527
|
FINISHED |
| Object | son of a Caddo chief |
—
|
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: son of a Caddo chief | Statement: [Nacogdoche, positionInLegend, son of a Caddo chief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInLegend Context triple: [Nacogdoche, positionInLegend, son of a Caddo chief]
-
A.
regionOfLegend
Indicates the geographic area or locale with which a particular legend or myth is associated.
-
B.
inLegendRole
chosen
Indicates that an entity appears in a legendary or mythic context fulfilling a specific narrative or symbolic role.
-
C.
reverseLegendPlacement
Indicates that the usual position of a legend in a visualization or layout is inverted or swapped to the opposite side or order.
-
D.
positionInShow
Indicates the specific order or placement an entity occupies within a show, series, or sequence of performances or episodes.
-
E.
chartPosition
Indicates the ranking or placement of an item within an ordered chart or list at a specific point in time.
- 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_69e245836014819091b91ed3074742a3 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1615d1fe081908079f777cdab12a2 |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:46 p.m.