Triple
T17934089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OSN |
E448406
|
entity |
| Predicate | associatedWithICAOCode |
P419
|
FINISHED |
| Object | RKSO |
—
|
NE NERFINISHED |
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: RKSO | Statement: [OSN, associatedWithICAOCode, RKSO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RKSO Context triple: [OSN, associatedWithICAOCode, RKSO]
-
A.
RKSO
chosen
RKSO is the ICAO airport code assigned to Osan Air Base, a major United States Air Force installation in South Korea.
-
B.
RKSP
RKSP is the abbreviation for the Roman Catholic State Party, a former Dutch political party that represented Catholic interests in the early 20th century.
-
C.
ROK
ROK is the stock ticker symbol for Rockwell Automation, a major U.S.-based industrial automation and information technology company.
-
D.
ROK
ROK is the IATA airport code for Rockhampton Airport, a regional airport serving the city of Rockhampton in Queensland, Australia.
-
E.
KOS
KOS is the vehicle registration code assigned to the town of Oświęcim in southern Poland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a5547b7881909dc41bb7dd34194f |
completed | April 19, 2026, 9:50 a.m. |
Created at: April 10, 2026, 10:21 a.m.