Triple
T35255331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mainland Ukraine |
E1018213
|
entity |
| Predicate | hasMajorRivers |
P165
|
FINISHED |
| Object | Dnieper River |
E41855
|
NE FINISHED |
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: Dnieper River | Statement: [mainland Ukraine, hasMajorRivers, Dnieper River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorRivers Context triple: [mainland Ukraine, hasMajorRivers, Dnieper River]
-
A.
hasMajorRiverSystem
Indicates that an entity possesses or is traversed by a primary, large-scale river network that significantly characterizes its hydrology or geography.
-
B.
hasNumberOfRivers
Indicates the quantitative relationship specifying how many rivers are associated with a given entity.
-
C.
isMajorRiver
Indicates that a river is classified as a major or significant river, typically based on factors like length, discharge, or geographic importance.
-
D.
hasRiver
chosen
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
hasMajorHydroSystem
Indicates that an entity possesses or is associated with a primary or significant hydrological system, such as a major river, watershed, or water network.
- F. None of above.
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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a02145017b08190bd424cc647c08d3b |
completed | May 11, 2026, 5:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3819d36fe08190bd4c6377ee547d89 |
completed | June 21, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_6a021338e2b08190980c489ee44c18b3 |
completed | May 11, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:02 p.m.