Triple
T36741777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creek Indian territory |
E907637
|
entity |
| Predicate | resultedInRelocationTo |
P1660
|
FINISHED |
| Object | Indian Territory (present-day Oklahoma) |
—
|
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: Indian Territory (present-day Oklahoma) | Statement: [Creek Indian territory, resultedInRelocationTo, Indian Territory (present-day Oklahoma)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultedInRelocationTo Context triple: [Creek Indian territory, resultedInRelocationTo, Indian Territory (present-day Oklahoma)]
-
A.
relocatedTo
chosen
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
B.
relocatedAfter
Indicates that one entity moved or was transferred to a new location after another specified event or relocation occurred.
-
C.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
-
D.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
-
E.
ultimatelyRelocatedWith
Indicates that one entity eventually moved to a new location together with another entity, resulting in them sharing the same final place.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:12 p.m.