Triple
T27901991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsawwassen–Duke Point route |
E705659
|
entity |
| Predicate | terminusOnVancouverIsland |
P168611
|
FINISHED |
| Object | Duke Point terminal |
—
|
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: Duke Point terminal | Statement: [Tsawwassen–Duke Point route, terminusOnVancouverIsland, Duke Point terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusOnVancouverIsland Context triple: [Tsawwassen–Duke Point route, terminusOnVancouverIsland, Duke Point terminal]
-
A.
terminusCanada
Indicates that something serves as an endpoint, destination, or terminal location within or specifically for Canada.
-
B.
terminusInland
Indicates that something ends, concludes, or has its final point within an inland area rather than at a coast or shoreline.
-
C.
terminusCoastal
Indicates that the endpoint or terminus of something (e.g., a route, line, or feature) is located on or directly adjacent to a coast.
-
D.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
E.
terminusEast
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 27, 2026, 6:42 p.m.