Triple
T19961044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC |
E479813
|
entity |
| Predicate | onboardServicesMayInclude |
P121590
|
FINISHED |
| Object | 1st class coaches |
—
|
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: 1st class coaches | Statement: [IC, onboardServicesMayInclude, 1st class coaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onboardServicesMayInclude Context triple: [IC, onboardServicesMayInclude, 1st class coaches]
-
A.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
B.
offeringMayInclude
Indicates that a particular offering can contain, comprise, or be associated with one or more specified components, items, or elements.
-
C.
benefitsMayInclude
Indicates that one entity lists or specifies possible advantages, gains, or positive outcomes that another entity may receive.
-
D.
hasPassengerAmenity
chosen
Indicates that an entity provides or is equipped with a specific amenity intended for the comfort or convenience of its passengers.
-
E.
carriedServices
Indicates that one entity provides, transports, or delivers specific services on behalf of or in support 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af4520c81909986a47289ba801e |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.