Triple
T18234435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guinness Peat Aviation |
E436632
|
entity |
| Predicate | aircraftTypeLeased |
P1524
|
FINISHED |
| Object | narrow-body 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: narrow-body jet airliners | Statement: [Guinness Peat Aviation, aircraftTypeLeased, narrow-body jet airliners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypeLeased Context triple: [Guinness Peat Aviation, aircraftTypeLeased, narrow-body jet airliners]
-
A.
aircraftType
chosen
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
poweredAircraftType
Indicates that one entity is a type or category of aircraft that is propelled by an onboard power source (e.g., engines), as opposed to being unpowered.
-
C.
aircraftUsedFromFleetOf
Indicates that a specific aircraft is selected and used from a particular fleet of aircraft.
-
D.
iataAircraftTypeCode
Indicates the standardized IATA code that specifies the aircraft type used in a flight or aviation context.
-
E.
carrierAircraft
Indicates that an aircraft is designed, equipped, or used to operate from an aircraft carrier.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b5ce608190b6fba518256607da |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:33 a.m.