Triple
T11651866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fly Jinnah |
E276922
|
entity |
| Predicate | fleetType |
P6198
|
FINISHED |
| Object | Airbus A320 |
E347772
|
NE 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: Airbus A320 | Statement: [Fly Jinnah, fleetType, Airbus A320]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Airbus A320 Context triple: [Fly Jinnah, fleetType, Airbus A320]
-
A.
Airbus A320-200
chosen
The Airbus A320-200 is a widely used narrow-body, twin-engine jet airliner designed for short- to medium-haul routes and operated by numerous airlines worldwide.
-
B.
Airbus A321
The Airbus A321 is a stretched, single-aisle commercial jet airliner widely used for short- to medium-haul passenger flights.
-
C.
Airbus A320 family
The Airbus A320 family is a widely used series of narrow-body, twin-engine jet airliners designed for short- to medium-haul commercial flights.
-
D.
Airbus A330
The Airbus A330 is a wide-body, twin-engine jet airliner designed for medium- to long-haul routes and widely used by airlines around the world.
-
E.
Airbus A319
The Airbus A319 is a short- to medium-range, narrow-body commercial airliner in the Airbus A320 family, widely used by airlines around the world for passenger services.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2d01f9c8190849f252f22519550 |
completed | April 10, 2026, 7:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f0191ced188190b79de079b6890221 |
completed | April 28, 2026, 2:19 a.m. |
Created at: April 8, 2026, 9:39 p.m.