Triple
T15721486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pialligo, Canberra |
E381104
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Canberra Airport |
E75538
|
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: Canberra Airport | Statement: [Pialligo, Canberra, near, Canberra Airport]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Canberra Airport Context triple: [Pialligo, Canberra, near, Canberra Airport]
-
A.
Canberra Airport
chosen
Canberra Airport is the main domestic and international airport serving Australia’s capital city, Canberra.
-
B.
Parkes Airport
Parkes Airport is a regional airport in New South Wales, Australia, serving the town of Parkes with domestic flights and general aviation services.
-
C.
Tullamarine Airport
Tullamarine Airport is the primary international and domestic airport serving Melbourne, Australia, and one of the country’s busiest aviation hubs.
-
D.
Griffith Airport
Griffith Airport is a regional airport serving the city of Griffith and the surrounding Riverina area in New South Wales, Australia.
-
E.
Albury Airport
Albury Airport is a regional airport in New South Wales, Australia, serving the city of Albury and surrounding areas with domestic flights.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb0b51081908e652ec4992296fa |
completed | April 16, 2026, 2:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a002d966ffc8190aa0d9d3abf8ad593 |
completed | May 10, 2026, 7:02 a.m. |
Created at: April 10, 2026, 4:45 a.m.