Triple
T8630972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A3ST |
E204399
|
entity |
| Predicate | aircraftCabinType |
P22937
|
FINISHED |
| Object | pressurized cargo hold |
—
|
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: pressurized cargo hold | Statement: [A3ST, aircraftCabinType, pressurized cargo hold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftCabinType Context triple: [A3ST, aircraftCabinType, pressurized cargo hold]
-
A.
seatClass
Indicates the travel or seating category assigned to a passenger or seat (e.g., economy, business, first class).
-
B.
hasCabinClass
Indicates that an entity (such as a booking, ticket, or seat) is associated with a specific cabin class (e.g., economy, business, first).
-
C.
cabinConfiguration
Indicates how the interior space of a vehicle, vessel, or aircraft is arranged and organized for occupants or cargo.
-
D.
pressurizedCabin
chosen
Indicates that an enclosed space, typically in a vehicle or structure, is maintained at a controlled air pressure different from the outside environment.
-
E.
seatCategory
Indicates the classification or type of a seat (e.g., by comfort level, price tier, or section) assigned to an 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.