Triple
T34718421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vidin–Calafat Bridge |
E1000840
|
entity |
| Predicate | locatedOnRiverKilometer |
P56863
|
FINISHED |
| Object | 796 |
—
|
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: 796 | Statement: [Vidin–Calafat Bridge, locatedOnRiverKilometer, 796]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnRiverKilometer Context triple: [Vidin–Calafat Bridge, locatedOnRiverKilometer, 796]
-
A.
riverKilometerContext
chosen
Indicates the position or context of something along a river, measured in river kilometers from a defined reference point.
-
B.
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).
-
C.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
-
D.
administrativeCenterOnRiver
Indicates that an administrative center (such as a capital or main governing city) is located on the banks of a specified river.
-
E.
riverineLocation
Indicates that something is located in, along, or directly associated with a river or river 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.