Triple
T8936382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 10 Light Rail Vehicle |
E212786
|
entity |
| Predicate | plannedServiceEntry |
P26282
|
FINISHED |
| Object | late 2020s |
—
|
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: late 2020s | Statement: [Type 10 Light Rail Vehicle, plannedServiceEntry, late 2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedServiceEntry Context triple: [Type 10 Light Rail Vehicle, plannedServiceEntry, late 2020s]
-
A.
plannedService
Indicates that a service is scheduled or intended to be provided, but has not yet occurred.
-
B.
plannedServiceType
Indicates the category or kind of service that has been scheduled or planned to be provided.
-
C.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
D.
plannedAt
chosen
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
E.
scheduledServiceType
Indicates the type or category of service that has been scheduled between entities (e.g., maintenance, appointment, or delivery).
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66928cec8190915636d663f843af |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:58 p.m.