Triple
T27835828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Morava Valley |
E703222
|
entity |
| Predicate | containsRiverSectionOf |
P116240
|
FINISHED |
| Object | Morava 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: Morava River | Statement: [Lower Morava Valley, containsRiverSectionOf, Morava River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRiverSectionOf Context triple: [Lower Morava Valley, containsRiverSectionOf, Morava River]
-
A.
watercourseSectionOf
Indicates that a watercourse segment forms a constituent part of a larger watercourse.
-
B.
downstreamRiverSection
Indicates that one river section is located downstream from, and receives flow from, another river section.
-
C.
includesHydrologicalSection
chosen
Indicates that one entity contains or encompasses a specific hydrological section as part of its spatial or structural extent.
-
D.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
-
E.
hasRiverConfluenceFunction
Indicates that something serves as a location or feature where two or more rivers meet and merge their flows.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 27, 2026, 5:59 p.m.