Triple
T18046413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardier REGIO |
E431786
|
entity |
| Predicate | serviceRange |
P117003
|
FINISHED |
| Object | short-distance passenger services |
—
|
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: short-distance passenger services | Statement: [Bombardier REGIO, serviceRange, short-distance passenger services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceRange Context triple: [Bombardier REGIO, serviceRange, short-distance passenger services]
-
A.
servicesType
chosen
Indicates the category or kind of services that one entity provides, uses, or is associated with in relation to another entity.
-
B.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
C.
servicesLine
Indicates that one entity provides or is associated with a particular service line or category of services for another entity.
-
D.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
E.
serviceIs
Indicates that one entity functions as a service of a specified type or category in relation to 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff2d3c48190875ffe9c042d3ec0 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.