Triple
T19834798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleksin |
E476560
|
entity |
| Predicate | hasRiverTransport |
P165
|
FINISHED |
| Object | Oka River navigation |
—
|
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: Oka River navigation | Statement: [Aleksin, hasRiverTransport, Oka River navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverTransport Context triple: [Aleksin, hasRiverTransport, Oka River navigation]
-
A.
waterTransport
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
-
B.
hasRiverPortPotential
Indicates that a location has suitable conditions to support the development or operation of a river port.
-
C.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
-
D.
hasRiver
chosen
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
transportsWaterFrom
Indicates that one entity carries or conveys water from a specified source entity to another location or entity.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e656d0e738819093000d3307962328 |
completed | April 20, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.