Triple
T23265022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J-Air |
E588121
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | XM |
—
|
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: XM | Statement: [J-Air, IATACode, XM]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: XM Context triple: [J-Air, IATACode, XM]
-
A.
XM
chosen
XM is the IATA airline designator assigned to J-Air, a regional commuter airline based in Japan and affiliated with Japan Airlines.
-
B.
XT
XT is a higher-end trim level of the Chrysler Laser sports hatchback, featuring upgraded equipment and performance-oriented options.
-
C.
CX
CX is the two-letter IATA airline designator used to identify Cathay Pacific in global aviation systems.
-
D.
CX
CX is a base trim level designation used by Buick for the Rendezvous crossover SUV, typically indicating a more entry-level configuration with standard features.
-
E.
MX
MX is the two-letter ISO 3166-1 alpha-2 country code that uniquely identifies Mexico in international standards and systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f194cc3b908190aaefd036aa2b52b5 |
completed | April 29, 2026, 5:19 a.m. |
Created at: April 17, 2026, 4:29 p.m.