Triple
T3655571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockhampton Airport |
E77520
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | ROK |
E77521
|
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: ROK | Statement: [Rockhampton Airport, IATAcode, ROK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ROK Context triple: [Rockhampton Airport, IATAcode, ROK]
-
A.
ROK
chosen
ROK is the IATA airport code for Rockhampton Airport, a regional airport serving the city of Rockhampton in Queensland, Australia.
-
B.
ROK
ROK is the stock ticker symbol for Rockwell Automation, a major U.S.-based industrial automation and information technology company.
-
C.
ROKN
ROKN is the abbreviation for the Republic of Korea Navy, the maritime branch of South Korea’s armed forces.
-
D.
ROKMC
ROKMC is the elite amphibious warfare branch of South Korea’s armed forces, known for rapid deployment and high-intensity combat capabilities.
-
E.
ROK Armed Forces
The ROK Armed Forces are the unified military forces of South Korea, responsible for the country's defense and security on land, at sea, and in the air.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3baf57c8190b72b5d1b910d9db6 |
completed | March 8, 2026, 6:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4883dc5408190a6e7e110acf03a15 |
completed | March 13, 2026, 9:57 p.m. |
Created at: March 8, 2026, 3:24 p.m.