Triple
T15004911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockhampton Airport |
E377683
|
entity |
| Predicate | hasICAOCode |
P419
|
FINISHED |
| Object | YBRK |
E377683
|
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: YBRK | Statement: [Rockhampton Airport, hasICAOCode, YBRK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YBRK Context triple: [Rockhampton Airport, hasICAOCode, YBRK]
-
A.
YBRK
chosen
YBRK is the ICAO airport code for Rockhampton Airport, a regional airport serving the city of Rockhampton in Queensland, Australia.
-
B.
YBRM
YBRM is the ICAO airport code for Broome International Airport in Western Australia, a regional hub serving the coastal town of Broome.
-
C.
YRK
YRK is the National Rail station code for York railway station, a major historic rail hub in North Yorkshire, England.
-
D.
BRG
BRG is the station code for Braga railway station, a major rail hub in the city of Braga in northern Portugal.
-
E.
BRG
BRG is the stock ticker symbol for Borregaard, a Norwegian company specializing in advanced and sustainable biochemicals derived from wood.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7322b5c81909089cbbf816e1436 |
completed | April 15, 2026, 12:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe96a04eec8190b347bf3637aba0bc |
completed | May 9, 2026, 2:06 a.m. |
Created at: April 10, 2026, 2:54 a.m.