Triple
T30248891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leibertingen |
E769137
|
entity |
| Predicate | hasRiverValleyNearby |
P40242
|
FINISHED |
| Object | Upper Danube valley |
—
|
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: Upper Danube valley | Statement: [Leibertingen, hasRiverValleyNearby, Upper Danube valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverValleyNearby Context triple: [Leibertingen, hasRiverValleyNearby, Upper Danube valley]
-
A.
hasRiverValley
chosen
Indicates that one location contains, includes, or is characterized by a river valley associated with another geographic feature or area.
-
B.
hasRiverValleyType
Indicates that an entity (such as a river or geographic area) is characterized by or associated with a specific type of river valley.
-
C.
locatedInRiverValley
Indicates that something is situated within the geographical area of a river valley.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
hasVillageOnRiver
Indicates that a village is located on or alongside a particular river.
- 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_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 29, 2026, 7:40 p.m.