Triple
T6694487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Korea Marine Corps |
E152713
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | ROKMC |
E81250
|
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: ROKMC | Statement: [Republic of Korea Marine Corps, shortName, ROKMC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ROKMC Context triple: [Republic of Korea Marine Corps, shortName, ROKMC]
-
A.
ROKMC
chosen
ROKMC is the elite amphibious warfare branch of South Korea’s armed forces, known for rapid deployment and high-intensity combat capabilities.
-
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.
ROCN
ROCN is the naval branch of Taiwan’s armed forces, responsible for maritime defense and security operations around the island and its surrounding waters.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6b196b300819095a194195ef9bd11 |
completed | March 27, 2026, 4:34 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6f7bba1008190a0ea11aabdb3f360 |
completed | March 27, 2026, 9:33 p.m. |
Created at: March 27, 2026, 2:05 p.m.