Triple
T7716146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MEA |
E174887
|
entity |
| Predicate | operatingAirlineCountryCode |
P12358
|
FINISHED |
| Object | LB |
—
|
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: LB | Statement: [MEA, operatingAirlineCountryCode, LB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingAirlineCountryCode Context triple: [MEA, operatingAirlineCountryCode, LB]
-
A.
linkedAirlineCountry
chosen
Indicates that there is an association between an airline and a country, such as the country where the airline is based, registered, or primarily operates.
-
B.
associatedAirlineICAOCode
Indicates the ICAO airline code that is linked to or used by the given entity (such as a flight, route, or service).
-
C.
operatedForAirline
Indicates that an aircraft or flight was operated on behalf of, or under the branding of, a particular airline.
-
D.
aircraftOperator
Indicates that one entity operates, manages, or is responsible for the use of a particular aircraft.
-
E.
primaryAircraftOperator
Indicates that one entity is the main organization or individual responsible for operating a particular aircraft.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.