Triple
T37977780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsoyaha |
E947469
|
entity |
| Predicate | relocatedWith |
P46455
|
FINISHED |
| Object | Muscogee (Creek) Nation |
—
|
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: Muscogee (Creek) Nation | Statement: [Tsoyaha, relocatedWith, Muscogee (Creek) Nation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocatedWith Context triple: [Tsoyaha, relocatedWith, Muscogee (Creek) Nation]
-
A.
relocatedUsing
Indicates that an entity was moved or transferred from one place to another by means of a specified method, tool, or transportation mode.
-
B.
relocated
Indicates that an entity has moved or been moved from one location or position to another.
-
C.
relocatedAfter
Indicates that one entity moved or was transferred to a new location after another specified event or relocation occurred.
-
D.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
E.
relocatedWithSupportFrom
chosen
Indicates that an entity moved or was transferred to a new location with assistance, backing, or resources provided by another entity.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.