Triple
T15086985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide Airport |
E360301
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | ADL |
E360301
|
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: ADL | Statement: [Adelaide Airport, hasIATACode, ADL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ADL Context triple: [Adelaide Airport, hasIATACode, ADL]
-
A.
ADL
chosen
ADL is the three-letter IATA airport code for Adelaide Airport, the main international and domestic airport serving Adelaide, South Australia.
-
B.
ADL Initiative
ADL Initiative is a U.S. Department of Defense-sponsored program that advances standards and technologies for distributed learning and training systems.
-
C.
ALD
ALD is the former railway station code used for Prayagraj Junction, a major rail hub in the Indian state of Uttar Pradesh.
-
D.
ADE
ADE is Apple's Automated Device Enrollment program that streamlines the setup and management of Apple devices in organizations through centralized, zero‑touch deployment.
-
E.
ADK
ADK is the National Rail station code for Ardwick railway station in Manchester, England.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00276d1608190bc310d5b86ecd1d5 |
completed | April 15, 2026, 9:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feae1ba4208190b1e8c55668a1b422 |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 10, 2026, 3:03 a.m.