Triple
T31428372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danube in Lower Austria |
E801727
|
entity |
| Predicate | hasRecreationalRouteAlongBanks |
P203310
|
FINISHED |
| Object | Danube Cycle Path |
—
|
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: Danube Cycle Path | Statement: [Danube in Lower Austria, hasRecreationalRouteAlongBanks, Danube Cycle Path]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationalRouteAlongBanks Context triple: [Danube in Lower Austria, hasRecreationalRouteAlongBanks, Danube Cycle Path]
-
A.
hasParkAlongBank
Indicates that a park is located adjacent to or running alongside the bank of a water body.
-
B.
hasRiverBankSettlement
Indicates that a settlement is located on or directly adjacent to the bank of a river.
-
C.
usesWaterwaysFor
Indicates that one entity relies on or employs waterways as a means or route to perform an activity or function in relation to another entity.
-
D.
riverPanorama
Indicates a wide, scenic view or visual representation that prominently features a river and its surrounding landscape.
-
E.
isUrbanWaterway
Indicates that a waterway is located within, passes through, or primarily serves an urban or metropolitan area.
- F. None of above. chosen
Provenance (4 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01531add1c8190b51add7bb046e2cb |
completed | May 11, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_6a014fef3d8c81909b509d51d0c4cdc7 |
completed | May 11, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_6a01531a3a4c8190ac8cb040cc36e96b |
completed | May 11, 2026, 3:55 a.m. |
Created at: April 30, 2026, 8:55 p.m.