Triple
T32975592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XY |
E843650
|
entity |
| Predicate | operatorAirlineCallsign |
P78301
|
FINISHED |
| Object | NAS EXPRESS |
—
|
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: NAS EXPRESS | Statement: [XY, operatorAirlineCallsign, NAS EXPRESS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAirlineCallsign Context triple: [XY, operatorAirlineCallsign, NAS EXPRESS]
-
A.
operatingAirlineCallsign
chosen
Indicates the radio callsign used by the airline that is actually operating the flight.
-
B.
airlineICAOcallsign
Indicates the official ICAO radio callsign phrase used to identify a specific airline in air traffic communications.
-
C.
airlineCommonName
Indicates the commonly used or publicly recognized name by which an airline is known.
-
D.
aircraftOperator
Indicates that one entity operates, manages, or is responsible for the use of a particular aircraft.
-
E.
hasUnderlyingAirlineCallsign
Indicates that an airline-related entity is associated with a specific underlying airline callsign used for identification 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
Created at: May 1, 2026, 1:22 a.m.