Triple
T10050320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OC Streetcar |
E207729
|
entity |
| Predicate | transitStyle |
P91835
|
FINISHED |
| Object | light-rail-style service |
—
|
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: light-rail-style service | Statement: [OC Streetcar, transitStyle, light-rail-style service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitStyle Context triple: [OC Streetcar, transitStyle, light-rail-style service]
-
A.
hasMTAStyle
Indicates that one entity possesses or is associated with a particular MTA (Mail Transfer Agent) configuration or style.
-
B.
rapidTransitSystem
Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
-
C.
transportTheme
Indicates that an agent or instrument moves or carries a theme (entity) from one place or state to another.
-
D.
appliesToTransitLine
Indicates that a rule, condition, or characteristic is specifically associated with and relevant to a particular transit line.
-
E.
metroSystemColor
Indicates the color assigned to a metro or subway line within a transit system.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf8e41c4819091fa12742197e207 |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:56 p.m.