Triple
T24048329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EC250 / SMILE |
E595582
|
entity |
| Predicate | passengerAmenities |
P121590
|
FINISHED |
| Object | air conditioning |
—
|
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: air conditioning | Statement: [EC250 / SMILE, passengerAmenities, air conditioning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerAmenities Context triple: [EC250 / SMILE, passengerAmenities, air conditioning]
-
A.
hasPassengerAmenity
chosen
Indicates that an entity provides or is equipped with a specific amenity intended for the comfort or convenience of its passengers.
-
B.
hasPassengerServicesTo
Indicates that a transportation provider operates passenger services connecting one location or entity to another.
-
C.
amenitiesInclude
Indicates that a place or facility provides or contains specific amenities as part of its features.
-
D.
passengerFacility
Indicates that a facility is designated for use by passengers, such as for boarding, waiting, or related passenger services.
-
E.
passengerConvenience
Indicates how convenient or comfortable a service, vehicle, or facility is for passengers to use.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9cedaa08190bf54857de1b312ed |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:18 p.m.