Triple
T12762014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCI D-Series coaches |
E305017
|
entity |
| Predicate | luggageStorage |
P13871
|
FINISHED |
| Object | underfloor luggage bays |
—
|
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: underfloor luggage bays | Statement: [MCI D-Series coaches, luggageStorage, underfloor luggage bays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: luggageStorage Context triple: [MCI D-Series coaches, luggageStorage, underfloor luggage bays]
-
A.
hasLuggage
Indicates that an entity is carrying, possessing, or associated with one or more pieces of luggage.
-
B.
hasBaggageClaim
Indicates that a location, typically a transportation hub, includes or provides a baggage claim area for retrieving luggage.
-
C.
airTransportableBy
Indicates that something can be transported or carried by air using a specific aircraft or air transport method.
-
D.
cargoSpace
chosen
Indicates that one entity provides storage capacity or room for carrying goods, equipment, or other items for another entity.
-
E.
usedInBaggageTags
Indicates that something (such as a code, identifier, or element) is employed or printed on baggage tags for identification or processing purposes.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8e44188190840cd23d380bf23d |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:28 p.m.