Triple
T24091943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munduruku |
E596807
|
entity |
| Predicate | primaryRiverRegion |
P155048
|
FINISHED |
| Object | Tapajós River |
—
|
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: Tapajós River | Statement: [Munduruku, primaryRiverRegion, Tapajós River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRiverRegion Context triple: [Munduruku, primaryRiverRegion, Tapajós River]
-
A.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
B.
riverRegion
Indicates that a river is located within, flows through, or is otherwise geographically associated with a particular region.
-
C.
majorRiverRole
Indicates that a river plays a primary or dominant role in a specified context, such as geography, economy, culture, or ecology, relative to other rivers in the area.
-
D.
hasHeadwatersOf
Indicates that a specified location or feature is the source or origin point of a particular river or watercourse.
-
E.
watercourseThroughRegion
Indicates that a watercourse (such as a river or stream) passes through or traverses a specified region.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd20134881908b9ba6069a708a92 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 10:53 p.m.