Triple
T1999803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EZY |
E43441
|
entity |
| Predicate | represents |
P129
|
FINISHED |
| Object | easyJet flights |
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 flights | Statement: [EZY, represents, easyJet flights]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: easyJet flights Context triple: [EZY, represents, easyJet flights]
-
A.
easyJet
chosen
easyJet is a major British low-cost airline operating extensive domestic and European routes.
-
B.
flyadeal
flyadeal is a Saudi low-cost airline based in Jeddah that operates domestic and regional flights as part of the Saudia Group.
-
C.
Jet2holidays
Jet2holidays is a UK-based package holiday provider offering flights, accommodation, and transfers to popular leisure destinations, primarily served by its sister airline Jet2.com.
-
D.
Jet2.com
Jet2.com is a British low-cost leisure airline that operates scheduled and charter flights across Europe from multiple UK bases.
-
E.
Flybe
Flybe was a British regional airline that operated short-haul flights across the UK and Europe before ceasing operations.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb87f78f0819098e787a5f3e062fd |
completed | March 7, 2026, 5:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae034122ec819096a72685b34c84b9 |
completed | March 8, 2026, 11:16 p.m. |
Created at: March 4, 2026, 7:37 p.m.