Triple
T23176486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM TDM series intercity coach |
E579017
|
entity |
| Predicate | operatorSegment |
P1670
|
FINISHED |
| Object | common carrier bus lines |
—
|
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: common carrier bus lines | Statement: [GM TDM series intercity coach, operatorSegment, common carrier bus lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorSegment Context triple: [GM TDM series intercity coach, operatorSegment, common carrier bus lines]
-
A.
operatedBySegment
Indicates that an operation, process, or service is carried out specifically by a particular segment or subsection of a larger system or route.
-
B.
operatorStart
Indicates the point in time or event at which an operator begins performing an action or process.
-
C.
operatesInSegment
chosen
Indicates that an entity conducts its activities or provides its services within a specified market or operational segment.
-
D.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
E.
operatorTask
Indicates that an operator is responsible for performing or managing a specific task.
- 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f6a8644819099b107bb13ea16ff |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:04 p.m.