Triple
T8991007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RUH |
E214786
|
entity |
| Predicate | isServedByAirlines |
P35742
|
FINISHED |
| Object | Flynas |
E232761
|
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: Flynas | Statement: [RUH, isServedByAirlines, Flynas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Flynas Context triple: [RUH, isServedByAirlines, Flynas]
-
A.
Flynas
chosen
Flynas is a Saudi low-cost airline based in Riyadh that operates domestic and regional flights across the Middle East and beyond.
-
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.
Aer Lingus
Aer Lingus is the flag carrier airline of Ireland, operating international flights primarily between Ireland, Europe, and North America.
-
E.
Crossair
Crossair was a former Swiss regional airline that served as the main predecessor to Swiss International Air Lines after the collapse of Swissair.
- 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_69ca83a05c608190bdfdbdb25e994b39 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc68733548819096a5ba0ff41e43da |
completed | April 1, 2026, 12:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfdb92ebf4819092b7ee94af16064b |
completed | April 3, 2026, 3:24 p.m. |
Created at: March 30, 2026, 7:04 p.m.