Triple
T11938924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roxas Airport |
E284123
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | RXS |
E876386
|
NE 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: RXS | Statement: [Roxas Airport, hasIATACode, RXS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RXS Context triple: [Roxas Airport, hasIATACode, RXS]
-
A.
RXS
chosen
RXS is the IATA airport code for Roxas Airport serving Roxas City in the Philippines.
-
B.
REXIS
REXIS is an X-ray imaging spectrometer aboard NASA’s OSIRIS-REx spacecraft designed to map elemental abundances on the surface of asteroid Bennu.
-
C.
RXA
RXA is the ICAO airline designator assigned to Rex Airlines, an Australian regional carrier.
-
D.
XRX
XRX is the stock ticker symbol for Xerox Holdings Corporation, an American company known for its document management technologies and printing solutions.
-
E.
IXS
IXS is the three-letter IATA airport code assigned to Silchar Airport in Assam, India.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903415d2481909d84e6727454b9fe |
completed | April 10, 2026, 2:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f4409a40dc81909d87c50601b98b78 |
completed | May 1, 2026, 5:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.