Triple
T20891330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Columbia Highway 1 |
E514412
|
entity |
| Predicate | openedAsPartOfTransCanada |
P141590
|
FINISHED |
| Object | 1962 |
—
|
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: 1962 | Statement: [British Columbia Highway 1, openedAsPartOfTransCanada, 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsPartOfTransCanada Context triple: [British Columbia Highway 1, openedAsPartOfTransCanada, 1962]
-
A.
formsLongestTransCanadaSegmentIn
Indicates that an entity constitutes the longest continuous segment of the Trans-Canada Highway within a specified region or jurisdiction.
-
B.
includesCanadianTerritoryPartially
Indicates that one entity geographically encompasses part, but not all, of the territory of Canada.
-
C.
regionCanadianSide
Indicates that the specified region is located on the Canadian side of a border or boundary.
-
D.
acquiredByCanada
Indicates that an entity was obtained, purchased, or otherwise brought under the ownership or control of Canada.
-
E.
roadOnCanadianSide
Indicates that the road is located on the Canadian side of a border or boundary.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05e307081908f1d044e877017ec |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:46 p.m.