Triple
T31617831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherkston |
E806810
|
entity |
| Predicate | hasAccessViaRoad |
P145268
|
FINISHED |
| Object | Ontario Highway 3 |
—
|
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: Ontario Highway 3 | Statement: [Sherkston, hasAccessViaRoad, Ontario Highway 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessViaRoad Context triple: [Sherkston, hasAccessViaRoad, Ontario Highway 3]
-
A.
hasAccessRoadsTo
chosen
Indicates that there exist one or more roads providing direct vehicular access from one location or site to another.
-
B.
hasPublicAccessAlongRoad
Indicates that something is accessible to the public from or along an adjacent road.
-
C.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
-
D.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
E.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
- 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_69f348d7883c8190b6c13ab92b7ef076 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 30, 2026, 10:39 p.m.