Triple
T32311050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Indian Springs (1825) |
E825499
|
entity |
| Predicate | effectOnCreeks |
P186975
|
FINISHED |
| Object | loss of ancestral homelands |
—
|
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: loss of ancestral homelands | Statement: [Treaty of Indian Springs (1825), effectOnCreeks, loss of ancestral homelands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnCreeks Context triple: [Treaty of Indian Springs (1825), effectOnCreeks, loss of ancestral homelands]
-
A.
waterwayEffect
Indicates how a waterway influences or impacts another entity, condition, or process.
-
B.
influenceOnRivers
Indicates the effect or impact that one entity has on the state, behavior, or condition of rivers.
-
C.
hasRiverInfluence
Indicates that one entity affects or is affected by a river in terms of its characteristics, behavior, or conditions.
-
D.
impactedRiver
Indicates that one entity has caused a significant effect, alteration, or disturbance to a river or its conditions.
-
E.
riverPhenomenon
Indicates a natural event, condition, or process that occurs in or directly affects a river.
- F. None of above. chosen
Provenance (4 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 1, 2026, 12:46 a.m.