Triple
T27222144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tocantins River |
E681304
|
entity |
| Predicate | notTributaryOf |
P162261
|
FINISHED |
| Object | Amazon 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: Amazon River | Statement: [Tocantins River, notTributaryOf, Amazon River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notTributaryOf Context triple: [Tocantins River, notTributaryOf, Amazon River]
-
A.
isNaturalTributaryOf
Indicates that one watercourse flows naturally into another, contributing its water as a tributary without artificial diversion.
-
B.
isHeadwaterTributaryOf
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
-
C.
hasTributaryRelationsWith
Indicates that one entity maintains a tributary relationship with another, typically involving regular payments or offerings in exchange for protection, favor, or acknowledgment of superiority.
-
D.
locatedOnTributaryOf
Indicates that one entity is situated along or on the banks of a tributary that flows into another specified water body.
-
E.
tributary
Indicates that one watercourse flows into and feeds another, contributing its water to a larger stream, river, or lake.
- 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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6262115408190a5e1da2ed416270d |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 9:43 a.m.