Triple
T1686570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voronezh |
E36454
|
entity |
| Predicate | hasRiverFunction |
P1477
|
FINISHED |
| Object | river port on the Voronezh River |
—
|
LITERAL 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: river port on the Voronezh River | Statement: [Voronezh, hasRiverFunction, river port on the Voronezh River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverFunction Context triple: [Voronezh, hasRiverFunction, river port on the Voronezh River]
-
A.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
B.
hasHydrologicalFunction
Indicates that something performs a role or action related to the movement, storage, or regulation of water within a hydrological system.
-
C.
hasRiverActivity
chosen
Indicates that an entity engages in, supports, or is associated with activities occurring on or along a river.
-
D.
isRiverInHydrologicalSense
Indicates that a river, considered as a hydrological feature (its water flow and drainage characteristics), is located within or associated with a specified geographic or hydrological area.
-
E.
hasMythicalRiverConfluence
Indicates a relationship where a mythical or legendary river is believed to merge or join with another river or body of water.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.