Triple
T24880814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RZO |
E622702
|
entity |
| Predicate | airlineCallsignIdentified |
P94347
|
FINISHED |
| Object | SATA |
—
|
NE NERFINISHED |
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: SATA | Statement: [RZO, airlineCallsignIdentified, SATA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineCallsignIdentified Context triple: [RZO, airlineCallsignIdentified, SATA]
-
A.
airlineICAOcallsign
Indicates the official ICAO radio callsign phrase used to identify a specific airline in air traffic communications.
-
B.
operatingAirlineCallsign
Indicates the radio callsign used by the airline that is actually operating the flight.
-
C.
hasUnderlyingAirlineCallsign
Indicates that an airline-related entity is associated with a specific underlying airline callsign used for identification in air traffic communications.
-
D.
callsignForIATACode
Indicates that a particular airline callsign is associated with a given IATA airline code.
-
E.
icaoCallsignFor
chosen
Indicates that one entity is the ICAO-assigned callsign used in air traffic communications for the other entity (typically an airline or aircraft operator).
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:24 a.m.