Triple
T30248664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scheer |
E769130
|
entity |
| Predicate | riverKilometreOnDanube |
P56863
|
FINISHED |
| Object | around 2,600 km from river source |
—
|
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: around 2,600 km from river source | Statement: [Scheer, riverKilometreOnDanube, around 2,600 km from river source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverKilometreOnDanube Context triple: [Scheer, riverKilometreOnDanube, around 2,600 km from river source]
-
A.
riverKilometerContext
chosen
Indicates the position or context of something along a river, measured in river kilometers from a defined reference point.
-
B.
borderingCountryAcrossDanube
Indicates that one country shares a border with another country specifically across the Danube River.
-
C.
riverLength
Indicates the measured extent of a river from its source to its mouth, typically expressed as a linear distance.
-
D.
waterwayLengthKilometres
Indicates the total length of a waterway, measured in kilometres.
-
E.
riverLengthContext
Indicates the contextual or situational information under which a river’s length is measured or considered.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 7:40 p.m.