Triple
T35546258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 56 Street |
E1027222
|
entity |
| Predicate | servesAsPrimaryRouteThrough |
P152997
|
FINISHED |
| Object | Tsawwassen |
—
|
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: Tsawwassen | Statement: [56 Street, servesAsPrimaryRouteThrough, Tsawwassen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsPrimaryRouteThrough Context triple: [56 Street, servesAsPrimaryRouteThrough, Tsawwassen]
-
A.
servesAsRouteTo
Indicates that one entity functions as a pathway, channel, or means of access leading to another entity.
-
B.
primaryRouteThrough
chosen
Indicates that one location or path serves as the main or most significant route passing through another location or area.
-
C.
hasPrimaryRoute
Indicates that one entity is designated as the main or principal route associated with another entity.
-
D.
servesAsBaseForRoute
Indicates that one entity functions as the foundational or starting point upon which a route is defined, constructed, or planned.
-
E.
isMostCommonRouteTo
Indicates that one route is the most frequently used or typical way to reach a particular destination or outcome compared to all other possible routes.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a001540d4f881908a4688881875e774 |
completed | May 10, 2026, 5:18 a.m. |
| PD | Predicate disambiguation | batch_6a0014a8cdd88190a67a90a2df2c5e18 |
completed | May 10, 2026, 5:16 a.m. |
Created at: May 3, 2026, 4:04 p.m.