Triple
T13418459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nowra Airport |
E313274
|
entity |
| Predicate | hasIATAcode |
P2569
|
FINISHED |
| Object | NOA |
E1038305
|
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: NOA | Statement: [Nowra Airport, hasIATAcode, NOA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NOA Context triple: [Nowra Airport, hasIATAcode, NOA]
-
A.
NOA
chosen
NOA is the IATA airport code for HMAS Albatross, a Royal Australian Navy air station located near Nowra, New South Wales.
-
B.
NOA
NOA is the three-letter National Rail station code for Newton-on-Ayr railway station in South Ayrshire, Scotland.
-
C.
NOH
NOH was the former abbreviation used for the New Orleans Hornets NBA franchise before it was rebranded as the New Orleans Pelicans.
-
D.
NOE
NOE is the regional vehicle registration code used on car license plates issued in the town of Olecko in northeastern Poland.
-
E.
NOE
NOE (Nucleo Operativo Ecologico) is a specialized unit of the Italian Carabinieri focused on investigating and combating environmental crimes and protecting ecological resources.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaeb8416c8190a00dde0917c26f51 |
completed | April 12, 2026, 2:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f73987cc088190839e8a589086639c |
completed | May 3, 2026, 12:03 p.m. |
Created at: April 9, 2026, 9:39 p.m.