Triple
T37101253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BC Highway 26 |
E918707
|
entity |
| Predicate | terminusAreaFeature |
P77353
|
FINISHED |
| Object | Barkerville Historic Town & Park |
—
|
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: Barkerville Historic Town & Park | Statement: [BC Highway 26, terminusAreaFeature, Barkerville Historic Town & Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusAreaFeature Context triple: [BC Highway 26, terminusAreaFeature, Barkerville Historic Town & Park]
-
A.
terminusAreaUse
Indicates how the area of a terminus (such as a station or endpoint facility) is utilized or functionally designated.
-
B.
terminusCityArea
Indicates that a city area serves as the terminal or end-point location for a route, line, or journey.
-
C.
terminusFeature
chosen
Indicates that a specific physical or structural feature is located at, marks, or characterizes the endpoint or terminus of something.
-
D.
terminusDistrict
Indicates the district or administrative area in which a route, line, or service ends or has its final terminus.
-
E.
cityCenterTerminusArea
Indicates that the referenced area serves as the terminus or end-point of a route or line located in or at the center of a city.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:14 p.m.