Triple
T27286010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AirTran Airways |
E688473
|
entity |
| Predicate | aircraftOrder |
P165383
|
FINISHED |
| Object | launch customer for Boeing 717 |
—
|
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: launch customer for Boeing 717 | Statement: [AirTran Airways, aircraftOrder, launch customer for Boeing 717]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftOrder Context triple: [AirTran Airways, aircraftOrder, launch customer for Boeing 717]
-
A.
aircraftOnOrder
Indicates that an aircraft has been requested or purchased but has not yet been delivered or entered into service.
-
B.
formerAircraftOrder
Indicates that an entity previously had an order for an aircraft, but that order is no longer current or active.
-
C.
aircraftInFleet
Indicates that a particular aircraft is included as a member of a specified fleet.
-
D.
aircraftIntroducedOfAircraft
Indicates that a specific aircraft model was introduced or entered service on a particular date or in a particular time period.
-
E.
appliedToAircraftBuiltBy
Indicates that something (such as a regulation, modification, or action) is applied specifically to aircraft that were built by a particular manufacturer or builder.
- F. None of above. chosen
Provenance (4 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_69ef355998e08190bdff849e8f33adce |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 11:11 a.m.