Triple
T28436669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran Aseman Airlines Flight 3704 |
E715285
|
entity |
| Predicate | ICAOairlineCode |
P26821
|
FINISHED |
| Object | IRC |
—
|
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: IRC | Statement: [Iran Aseman Airlines Flight 3704, ICAOairlineCode, IRC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ICAOairlineCode Context triple: [Iran Aseman Airlines Flight 3704, ICAOairlineCode, IRC]
-
A.
airlineICAOcallsign
Indicates the official ICAO radio callsign phrase used to identify a specific airline in air traffic communications.
-
B.
ICAOcode
Indicates that an entity is identified by a specific four-letter airport or aerodrome code assigned by the International Civil Aviation Organization (ICAO).
-
C.
IATAcode
Indicates the three-letter IATA airport or airline code assigned to the entity.
-
D.
associatedAirlineICAOCode
chosen
Indicates the ICAO airline code that is linked to or used by the given entity (such as a flight, route, or service).
-
E.
operatingAirlineICAOCode
Indicates the ICAO airline designator code of the airline that is actually operating the flight or service.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e3a2c18819085f3e19fa534da4c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:43 a.m.