Triple
T35935255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Village of Kincaid |
E1039284
|
entity |
| Predicate | hasRoadAccessInProvince |
P197813
|
FINISHED |
| Object | Saskatchewan |
—
|
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: Saskatchewan | Statement: [Village of Kincaid, hasRoadAccessInProvince, Saskatchewan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadAccessInProvince Context triple: [Village of Kincaid, hasRoadAccessInProvince, Saskatchewan]
-
A.
hasAccessRoadsTo
Indicates that there exist one or more roads providing direct vehicular access from one location or site to another.
-
B.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
C.
hasPublicAccessAlongRoad
Indicates that something is accessible to the public from or along an adjacent road.
-
D.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
E.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
- F. None of above. chosen
Provenance (4 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
| PDg | Predicate description generation | batch_69feabcca6148190a8eb7b6fa33729c7 |
completed | May 9, 2026, 3:36 a.m. |
Created at: May 3, 2026, 4:07 p.m.