Triple
T2176884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O-Train |
E48549
|
entity |
| Predicate | originalServiceType |
P4682
|
FINISHED |
| Object | diesel light rail |
—
|
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: diesel light rail | Statement: [O-Train, originalServiceType, diesel light rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalServiceType Context triple: [O-Train, originalServiceType, diesel light rail]
-
A.
originalType
chosen
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
-
B.
originalBusinessType
Indicates the initial or primary category of business activity or industry classification associated with an entity before any subsequent changes or reclassifications.
-
C.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to another entity.
-
D.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
E.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc4358fc88190a6f556c2de9fef8c |
completed | March 7, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69abbda0ec948190be88c1243d81a423 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.