Triple
T4292837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yacyretá Dam |
E99635
|
entity |
| Predicate | hasFishPass |
P50032
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Yacyretá Dam, hasFishPass, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFishPass Context triple: [Yacyretá Dam, hasFishPass, yes]
-
A.
hasFishPassage
Indicates that there exists a structure or feature that allows fish to move or migrate through, past, or around a barrier such as a dam or weir.
-
B.
hasFishingSpecies
Indicates that a location, body of water, or fishing area supports or contains one or more specific species that can be fished there.
-
C.
hasPrimaryFishSpecies
Indicates that an entity is characterized by or associated with a particular main or dominant fish species.
-
D.
fishPassage
chosen
Indicates that a water structure or feature allows fish to move or migrate through or past it.
-
E.
hasFishCountingFacility
Indicates that a location or structure is equipped with a facility specifically designed for counting fish.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35082228081908504e3fd7c4ca1e8 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.