Triple
T14731782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intercity H set (OSCAR) |
E346092
|
entity |
| Predicate | introducedForServiceType |
P53961
|
FINISHED |
| Object | intercity 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: intercity services | Statement: [Intercity H set (OSCAR), introducedForServiceType, intercity services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedForServiceType Context triple: [Intercity H set (OSCAR), introducedForServiceType, intercity services]
-
A.
introducedForServiceWith
Indicates that one entity was presented or brought to the attention of another entity specifically for the purpose of providing a service.
-
B.
appliesToServiceType
chosen
Indicates that something is relevant or applicable specifically to a particular type or category of service.
-
C.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
D.
serviceIntroduced
Indicates that a particular service has been launched, made available, or brought into operation at a certain time or context.
-
E.
introducedAsType
Indicates that one entity is presented or identified to others as having a particular role, category, or type.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec26311c8819093a81ff0fa43b33b |
completed | April 14, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:29 a.m.