Triple
T29063445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queensville |
E735602
|
entity |
| Predicate | hasProvinceHighwayExit |
P12245
|
FINISHED |
| Object | Highway 404 Queensville Sideroad interchange |
—
|
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: Highway 404 Queensville Sideroad interchange | Statement: [Queensville, hasProvinceHighwayExit, Highway 404 Queensville Sideroad interchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProvinceHighwayExit Context triple: [Queensville, hasProvinceHighwayExit, Highway 404 Queensville Sideroad interchange]
-
A.
expresswayServedBy
Indicates that a particular expressway is provided with service or access by a specified facility, route, or service entity.
-
B.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
C.
hasStreetExits
Indicates that a location or structure has one or more exits that lead directly onto a street.
-
D.
connectsToHighway
chosen
Indicates that one location, road, or route has a direct access point or linkage to a highway.
-
E.
hasExpresswayName
Indicates that an entity (such as a road segment or route) is associated with a specific expressway name.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: April 28, 2026, 10:16 a.m.