Triple
T33699256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mirna River (nearby confluence) |
E863407
|
entity |
| Predicate | watercourseFlowsNear |
P8567
|
FINISHED |
| Object | Sevnica |
—
|
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: Sevnica | Statement: [Mirna River (nearby confluence), watercourseFlowsNear, Sevnica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watercourseFlowsNear Context triple: [Mirna River (nearby confluence), watercourseFlowsNear, Sevnica]
-
A.
nearbyWatercourse
chosen
Indicates that one entity is located close to or alongside a natural or artificial watercourse, such as a river, stream, or canal.
-
B.
riverTypeNearby
Indicates that one entity is located near a river of a specified type or classification.
-
C.
watercourseFor
Indicates that one entity serves as the watercourse (such as a river or channel) associated with, carrying, or draining another entity.
-
D.
nearbyRiverProject
Indicates that there is a project located close to or associated with a nearby river.
-
E.
watercourseSupports
Indicates that a watercourse provides the necessary conditions or resources to sustain another entity, process, or activity.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 1, 2026, 1:43 a.m.