Triple
T19834972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suvorov |
E476564
|
entity |
| Predicate | railOrRoadAccess |
P124024
|
FINISHED |
| Object | regional road network of Tula Oblast |
—
|
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: regional road network of Tula Oblast | Statement: [Suvorov, railOrRoadAccess, regional road network of Tula Oblast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railOrRoadAccess Context triple: [Suvorov, railOrRoadAccess, regional road network of Tula Oblast]
-
A.
hasRailOrRoadAccess
chosen
Indicates that an entity is connected to or reachable by either a railway network, a road network, or both.
-
B.
railAccessModel
Indicates the type or pattern of how rail infrastructure or services are accessed or connected between locations or entities.
-
C.
railwayAccess
Indicates that an entity has direct access to, connection with, or service by a railway line or station.
-
D.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
E.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
- 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.