Triple
T13419021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribera del Duero |
E313288
|
entity |
| Predicate | regionLengthAlongRiver |
P91898
|
FINISHED |
| Object | about 115 km |
—
|
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: about 115 km | Statement: [Ribera del Duero, regionLengthAlongRiver, about 115 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionLengthAlongRiver Context triple: [Ribera del Duero, regionLengthAlongRiver, about 115 km]
-
A.
hasApproxLengthAlongRiver
chosen
Indicates that an entity has an approximate measured length that follows the course of a river rather than a straight-line distance.
-
B.
riverKilometerContext
Indicates the position or context of something along a river, measured in river kilometers from a defined reference point.
-
C.
waterwayLengthKilometres
Indicates the total length of a waterway, measured in kilometres.
-
D.
positionInRiverSystem
Indicates the relative location or order of a water body or feature within the hierarchical structure of a river system (e.g., upstream, downstream, tributary level).
-
E.
locatedBetweenRiver
Indicates that an entity is situated in the area or region between two segments or banks of a river, or between two rivers.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaeb8416c8190a00dde0917c26f51 |
completed | April 12, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:39 p.m.