Triple
T11525016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AUA |
E273270
|
entity |
| Predicate | associatedAirlineICAOCallsign |
P95732
|
FINISHED |
| Object | AUSTRIAN |
—
|
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: AUSTRIAN | Statement: [AUA, associatedAirlineICAOCallsign, AUSTRIAN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirlineICAOCallsign Context triple: [AUA, associatedAirlineICAOCallsign, AUSTRIAN]
-
A.
associatedAirlineICAOCode
Indicates the ICAO airline code that is linked to or used by the given entity (such as a flight, route, or service).
-
B.
associatedAirlineFullName
Indicates the full official name of the airline that is associated with a given entity or record.
-
C.
associatedAirlineIATA
Indicates the IATA airline code that is linked or related to a given entity (such as a flight, route, or airport record).
-
D.
operatingAirlineCallsign
Indicates the radio callsign used by the airline that is actually operating the flight.
-
E.
airlineICAOcallsign
chosen
Indicates the official ICAO radio callsign phrase used to identify a specific airline in air traffic communications.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd379648190b342e0c4b4f685b7 |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.