Triple
T16285837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROKA insignia |
E395385
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | ROKA |
E395378
|
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: ROKA | Statement: [ROKA insignia, hasAbbreviation, ROKA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ROKA Context triple: [ROKA insignia, hasAbbreviation, ROKA]
-
A.
ROKA
chosen
ROKA is the commonly used abbreviation for the Republic of Korea Army, the land warfare branch of South Korea’s armed forces.
-
B.
ROK
ROK is the IATA airport code for Rockhampton Airport, a regional airport serving the city of Rockhampton in Queensland, Australia.
-
C.
ROK
ROK is the stock ticker symbol for Rockwell Automation, a major U.S.-based industrial automation and information technology company.
-
D.
ROKAF
ROKAF is the air warfare branch of South Korea’s armed forces, responsible for the country’s aerial defense and air operations.
-
E.
ROKN
ROKN is the abbreviation for the Republic of Korea Navy, the maritime branch of South Korea’s armed forces.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24914bda08190a5d6315414ee3f76 |
completed | April 17, 2026, 2:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a001f94ede48190835e8a0c6f5d0f19 |
completed | May 10, 2026, 6:03 a.m. |
Created at: April 10, 2026, 5:05 a.m.