Triple
T25672779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danubian Lowland |
E643722
|
entity |
| Predicate | isMajorBasinOf |
P163824
|
FINISHED |
| Object | Danube River |
—
|
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 River | Statement: [Danubian Lowland, isMajorBasinOf, Danube River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorBasinOf Context triple: [Danubian Lowland, isMajorBasinOf, Danube River]
-
A.
isPrincipalBasinOf
chosen
Indicates that one basin serves as the main or primary drainage basin associated with another geographic or hydrologic feature.
-
B.
hasMajorCityOnBasin
Indicates that a major city is located on or within the drainage basin of a specified water system.
-
C.
hasMajorOutflowBasin
Indicates that a geographic feature (such as a water body or watershed) has a specific basin into which most or all of its water ultimately flows.
-
D.
basinPartOf
Indicates that one basin is a component or subdivision of a larger basin or basin system.
-
E.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 21, 2026, 7:31 p.m.