Triple
T29005248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viva stations |
E736412
|
entity |
| Predicate | inServiceFor |
P47372
|
FINISHED |
| Object | York Region Transit passengers |
—
|
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: York Region Transit passengers | Statement: [Viva stations, inServiceFor, York Region Transit passengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inServiceFor Context triple: [Viva stations, inServiceFor, York Region Transit passengers]
-
A.
inService
Indicates that an entity is currently active, operational, or available for use in its intended role or function.
-
B.
inServiceFrom
Indicates the time or event from which an entity (such as a service, system, or asset) begins being operationally active or officially in use.
-
C.
continuedInServiceOn
Indicates that an entity remained active, operational, or in use beyond a specified point in time or event.
-
D.
usedForService
chosen
Indicates that one entity is employed, utilized, or designated to perform, support, or provide a particular service for another entity.
-
E.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f65fbf80948190bd059c9584ac705e |
completed | May 2, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:37 a.m.