Triple
T12294479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embraer 195 |
E293047
|
entity |
| Predicate | IATAMaxSeatingCategory |
P84520
|
FINISHED |
| Object | single-aisle jet |
—
|
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: single-aisle jet | Statement: [Embraer 195, IATAMaxSeatingCategory, single-aisle jet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IATAMaxSeatingCategory Context triple: [Embraer 195, IATAMaxSeatingCategory, single-aisle jet]
-
A.
hasSeatingCapacityCategory
Indicates the classification of an entity based on the range or category of how many people it can seat.
-
B.
seatCategory
Indicates the classification or type of a seat (e.g., by comfort level, price tier, or section) assigned to an entity.
-
C.
aircraftSeatingCategory
chosen
Indicates the classification of an aircraft’s seating arrangement or capacity type associated with an entity.
-
D.
seatingCapacity
Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
-
E.
classesOfSeats
Indicates the different categories or types of seats associated with something, such as a venue, vehicle, or event.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:52 p.m.