Triple
T31597240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embraer Praetor 500 |
E806249
|
entity |
| Predicate | hasCabinZone |
P12453
|
FINISHED |
| Object | club seating area |
—
|
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: club seating area | Statement: [Embraer Praetor 500, hasCabinZone, club seating area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCabinZone Context triple: [Embraer Praetor 500, hasCabinZone, club seating area]
-
A.
hasCabinClass
Indicates that an entity (such as a booking, ticket, or seat) is associated with a specific cabin class (e.g., economy, business, first).
-
B.
hasCabins
chosen
Indicates that an entity possesses or includes one or more cabins as part of its structure or facilities.
-
C.
cabinConfiguration
Indicates how the interior space of a vehicle, vessel, or aircraft is arranged and organized for occupants or cargo.
-
D.
hasCabPosition
Indicates that an entity has a specific position or placement of a cab relative to its overall structure or configuration.
-
E.
hasPassengerArea
Indicates that an object or vehicle includes a designated area intended for carrying passengers.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 30, 2026, 10:31 p.m.