Triple
T34154615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Vancouver public transit network |
E876098
|
entity |
| Predicate | smartCardSystemLaunchYear |
P3297
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Metro Vancouver public transit network, smartCardSystemLaunchYear, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smartCardSystemLaunchYear Context triple: [Metro Vancouver public transit network, smartCardSystemLaunchYear, 2015]
-
A.
screenDebutYear
Indicates the year in which an entity first appeared on screen (such as in film, television, or other recorded visual media).
-
B.
cardBrandLaunch
Indicates the event or action of introducing a new card brand into the market or making it officially available for use.
-
C.
introducedInYear
chosen
Indicates the year in which something was first introduced, launched, or made available.
-
D.
yearOfIssue
Indicates the specific calendar year in which something (such as a document, publication, or item) was formally issued or released.
-
E.
firstPublicUseYear
Indicates the calendar year in which something was first made available for use by the public.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70fb5ae4c8190a6c0e578edfa60ce |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:54 a.m.