Triple
T30972575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebro Treaty |
E789137
|
entity |
| Predicate | boundaryRiver |
P75268
|
FINISHED |
| Object | Ebro 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: Ebro River | Statement: [Ebro Treaty, boundaryRiver, Ebro River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryRiver Context triple: [Ebro Treaty, boundaryRiver, Ebro River]
-
A.
transboundaryRiverOf
Indicates that a river crosses or forms the boundary between two or more political or administrative regions.
-
B.
bordersAcrossRiver
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
-
C.
borderingWaters
Indicates that a geographic area directly touches or is adjacent to a particular body of water.
-
D.
betweenRiver
Indicates a spatial relationship where something is located in the area separating two rivers or lies in the intermediate region defined by them.
-
E.
borderRiverContext
chosen
Indicates that a river serves as or is involved in forming the boundary between two geographic or political regions within a specific contextual setting.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:55 p.m.