Triple
T35690477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyšné Nemecké–Uzhhorod road crossing |
E1031273
|
entity |
| Predicate | isOnNationalRoad |
P143312
|
FINISHED |
| Object | Slovak road I/50 |
—
|
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: Slovak road I/50 | Statement: [Vyšné Nemecké–Uzhhorod road crossing, isOnNationalRoad, Slovak road I/50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnNationalRoad Context triple: [Vyšné Nemecké–Uzhhorod road crossing, isOnNationalRoad, Slovak road I/50]
-
A.
hasNationalRoad
Indicates that a location is connected to or served by a designated national road within a country's official road network.
-
B.
isSegmentOfNationalRoute
chosen
Indicates that a road segment forms part of a designated national route within a country's road network.
-
C.
isLocatedOnHighway
Indicates that one entity is situated along, adjacent to, or directly accessible from a specific highway.
-
D.
isPublicRoad
Indicates that a given road is officially designated and accessible for use by the general public.
-
E.
isNamedRoadIn
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
- 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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.