Triple
T14795766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airbus A320-200 |
E347772
|
entity |
| Predicate | typicalAirlines |
P16896
|
FINISHED |
| Object | easyJet |
E6907
|
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: easyJet | Statement: [Airbus A320-200, typicalAirlines, easyJet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: easyJet Context triple: [Airbus A320-200, typicalAirlines, easyJet]
-
A.
easyJet
chosen
easyJet is a major British low-cost airline operating extensive domestic and European routes.
-
B.
Ryanair
Ryanair is a major Irish low-cost airline known for its extensive network of short-haul flights across Europe.
-
C.
Flybe
Flybe was a British regional airline that operated short-haul flights across the UK and Europe before ceasing operations.
-
D.
Wizz Air
Wizz Air is a Hungarian ultra-low-cost airline known for operating an extensive network of budget flights across Europe and surrounding regions.
-
E.
EasyFly
EasyFly is a Colombian regional airline that operates domestic flights connecting smaller cities and regional hubs across the country.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5fdd548190a2ee5e668c2b20b4 |
completed | April 14, 2026, 11:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe24c0beb0819081a124479a849bb6 |
completed | May 8, 2026, 6 p.m. |
Created at: April 10, 2026, 1:31 a.m.