Triple
T36741756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creek Indian territory |
E907637
|
entity |
| Predicate | preRemovalHomelandOf |
P130032
|
FINISHED |
| Object | Muscogee (Creek) people |
—
|
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) people | Statement: [Creek Indian territory, preRemovalHomelandOf, Muscogee (Creek) people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preRemovalHomelandOf Context triple: [Creek Indian territory, preRemovalHomelandOf, Muscogee (Creek) people]
-
A.
hasHomeland
Indicates that an entity considers or recognizes a particular place or region as its homeland or place of origin.
-
B.
wasHomelandIn
chosen
Indicates that a location historically served as the homeland or place of origin for a specified group or entity.
-
C.
recognizedHomelandsPolicy
Indicates that an authority formally acknowledges and accepts a specific homelands policy as valid or in effect.
-
D.
preRemovalSocietyType
Indicates the type or classification of a society or social structure that existed before a removal event or process occurred.
-
E.
accessToHomeland
Indicates that an entity has the ability, right, or means to enter, return to, or be present in its homeland.
- 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_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.