Triple
T16750074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASL |
E407049
|
entity |
| Predicate | airlineMainHubAirportCodeICAO |
P115047
|
FINISHED |
| Object | LYBE |
—
|
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: LYBE | Statement: [ASL, airlineMainHubAirportCodeICAO, LYBE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineMainHubAirportCodeICAO Context triple: [ASL, airlineMainHubAirportCodeICAO, LYBE]
-
A.
ICAOcode
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
B.
operatorPrimaryHubAirportCode
chosen
Indicates the airport code of the main or primary hub used by the operator.
-
C.
associatedAirportPrimaryHubFor
Indicates that an airport serves as the primary hub for a particular airline or transportation operator.
-
D.
associatedAirlineHeadquarters
Indicates that an airline is connected to or based at a particular headquarters location.
-
E.
servesAsPrimaryAirportOperatorForCity
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa265a908190a87fa4612bfe6396 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.