Triple
T5661745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newfound Gap |
E124757
|
entity |
| Predicate | roadOpen |
P38961
|
FINISHED |
| Object | generally year-round, weather permitting |
—
|
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 year-round, weather permitting | Statement: [Newfound Gap, roadOpen, generally year-round, weather permitting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadOpen Context triple: [Newfound Gap, roadOpen, generally year-round, weather permitting]
-
A.
openedToRoadTraffic
Indicates that something, such as a structure or route, has begun allowing regular use by vehicles or road users.
-
B.
isPublicRoad
Indicates that a given road is officially designated and accessible for use by the general public.
-
C.
isRoadAccessible
chosen
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
D.
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.
-
E.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
- 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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:42 p.m.