Triple
T37914597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Čertovica |
E945779
|
entity |
| Predicate | roadOpenAllYear |
P178151
|
FINISHED |
| Object | generally yes |
—
|
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: generally yes | Statement: [Čertovica, roadOpenAllYear, generally yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadOpenAllYear Context triple: [Čertovica, roadOpenAllYear, generally yes]
-
A.
openedForYearRoundTraffic
Indicates that something has been made accessible and usable for traffic throughout the entire year, without seasonal closures.
-
B.
roadAccessSeason
Indicates the time of year or season during which road access to a place or area is available or permitted.
-
C.
isAllYearRoad
chosen
Indicates that a road remains accessible and usable throughout the entire year, regardless of seasonal or weather conditions.
-
D.
accessibleYearRound
Indicates that the subject can be accessed or used during all seasons of the year without interruption.
-
E.
openedForThroughTraffic
Indicates that a route or segment is available and accessible for vehicles to pass through (not just for local access), allowing continuous through traffic.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.