Triple
T25473580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enawené-Nawé |
E638368
|
entity |
| Predicate | riverineAssociation |
P72732
|
FINISHED |
| Object | Juruena River basin |
—
|
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: Juruena River basin | Statement: [Enawené-Nawé, riverineAssociation, Juruena River basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverineAssociation Context triple: [Enawené-Nawé, riverineAssociation, Juruena River basin]
-
A.
closelyAssociatedRiver
Indicates a river that is geographically or functionally closely connected to the subject, such as flowing nearby, through, or otherwise strongly linked to it.
-
B.
associatedRiverBasin
chosen
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
C.
mainRiverAssociated
Indicates that one entity is associated with, or primarily linked to, a particular main river.
-
D.
associatedWithWaterways
Indicates a relationship in which something is connected, linked, or relevant to waterways such as rivers, canals, or streams.
-
E.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 21, 2026, 2:25 p.m.