Triple
T25565077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Txingudi Bay |
E640812
|
entity |
| Predicate | borderRiverEstuaryOf |
P101371
|
FINISHED |
| Object | Bidasoa 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: Bidasoa River | Statement: [Txingudi Bay, borderRiverEstuaryOf, Bidasoa River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRiverEstuaryOf Context triple: [Txingudi Bay, borderRiverEstuaryOf, Bidasoa River]
-
A.
borderedBySeaViaRiverMouth
chosen
Indicates that a place is bordered by the sea specifically at the point where a river flows into it (its river mouth).
-
B.
estuaryName
Indicates the naming relationship that assigns a specific name to an estuary.
-
C.
riverMouthRegion
Indicates the region or area where a river flows into a larger body of water, such as a sea, lake, or another river.
-
D.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
E.
riverMouthBasin
Indicates that a river’s mouth lies within or drains into a particular drainage basin.
- 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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 3:48 p.m.