Triple
T38513984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yazoo people |
E921989
|
entity |
| Predicate | riverinePeopleOf |
P56551
|
FINISHED |
| Object | Mississippi |
—
|
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: Mississippi | Statement: [Yazoo people, riverinePeopleOf, Mississippi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverinePeopleOf Context triple: [Yazoo people, riverinePeopleOf, Mississippi]
-
A.
riverinePeople
chosen
Indicates a relationship where people live along, depend on, or are closely associated with rivers and river environments.
-
B.
riverineSettlement
Indicates that a settlement is located on or closely associated with the banks or course of a river.
-
C.
colonialRiverName
Indicates that a river has or is associated with a name given during a colonial period, as opposed to its indigenous or pre-colonial name.
-
D.
riverineLocation
Indicates that something is located in, along, or directly associated with a river or river system.
-
E.
useRiverSystems
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.