Triple
T13475474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MALAYSIAN THREE SEVEN ZERO |
E318238
|
entity |
| Predicate | operatingCarrierCallsignPrefix |
P94340
|
FINISHED |
| Object | MALAYSIAN |
—
|
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: MALAYSIAN | Statement: [MALAYSIAN THREE SEVEN ZERO, operatingCarrierCallsignPrefix, MALAYSIAN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingCarrierCallsignPrefix Context triple: [MALAYSIAN THREE SEVEN ZERO, operatingCarrierCallsignPrefix, MALAYSIAN]
-
A.
operatingAirlineCallsign
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.
operatesAsRegionalCarrierFor
Indicates that one transportation company functions as a regional carrier on behalf of another, typically providing local or feeder services under the larger company’s brand or network.
-
D.
aircraftOperator
Indicates that one entity operates, manages, or is responsible for the use of a particular aircraft.
-
E.
hasCallSignPrefix
chosen
Indicates that an entity’s call sign begins with a specified prefix.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf2551b48190a074fd256791742d |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.