Triple
T1543356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOUTHWEST |
E32920
|
entity |
| Predicate | usedByAircraftType |
P30181
|
FINISHED |
| Object | jet airliners |
—
|
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: jet airliners | Statement: [SOUTHWEST, usedByAircraftType, jet airliners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByAircraftType Context triple: [SOUTHWEST, usedByAircraftType, jet airliners]
-
A.
usedOnAircraftName
Indicates that something is employed or applied on an aircraft identified by a specific name.
-
B.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
C.
aircraftTypesCarried
Indicates that one entity (typically a vessel, facility, or platform) carries or is capable of carrying specific types of aircraft as part of its operations or configuration.
-
D.
aircraftManufacturerUsed
Indicates that a particular aircraft manufacturer was employed or utilized in relation to another entity, such as for production, design, or supply purposes.
-
E.
carrierAircraft
Indicates that an aircraft is designed, equipped, or used to operate from an aircraft carrier.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa95c1a2948190a2b98469afec1a7d |
completed | March 6, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69a907b2453c8190a41f6b88c8217d1e |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a93df847cc8190b6d011af33b34b40 |
completed | March 5, 2026, 8:25 a.m. |
Created at: March 4, 2026, 7:26 p.m.