Triple
T31643591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancistrus cirrhosus |
E807523
|
entity |
| Predicate | foundInRiverBasin |
P72732
|
FINISHED |
| Object | Paraná River basin |
—
|
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: Paraná River basin | Statement: [Ancistrus cirrhosus, foundInRiverBasin, Paraná River basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInRiverBasin Context triple: [Ancistrus cirrhosus, foundInRiverBasin, Paraná River basin]
-
A.
locatedInBasin
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
-
B.
associatedRiverBasin
chosen
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
C.
hasHeadwatersIn
Indicates that the source or origin of a river, stream, or similar watercourse is located within a specified geographic area or feature.
-
D.
hasHeadwatersOf
Indicates that a specified location or feature is the source or origin point of a particular river or watercourse.
-
E.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 30, 2026, 10:50 p.m.