Triple
T3747861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROKMC |
E81250
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 대한민국 해병대 |
E81249
|
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: 대한민국 해병대 | Statement: [ROKMC, nativeName, 대한민국 해병대]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 대한민국 해병대 Context triple: [ROKMC, nativeName, 대한민국 해병대]
-
A.
대한민국 해병대
chosen
대한민국 해병대는 상륙작전과 신속 대응 임무를 주 임무로 하는 대한민국 국군의 해병 전투 병과이다.
-
B.
제1해병사단
제1해병사단은 상륙작전과 기동전 수행을 주 임무로 하는 대한민국 해병대의 핵심 전력 사단이다.
-
C.
Republic of Korea Marine Corps
The Republic of Korea Marine Corps is South Korea’s elite amphibious and expeditionary warfare force, known for rapid deployment and high-intensity combat capabilities.
-
D.
제9해병여단
제9해병여단은 대한민국 해병대 예하에서 서북도서 및 서해 방어 임무 등을 수행하는 전투 여단급 부대이다.
-
E.
Inchon Regiment
The Inchon Regiment is a nickname for the U.S. Marine Corps' 1st Marine Regiment, commemorating its pivotal role in the 1950 amphibious landing at Inchon during the Korean War.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb6ac5ac8190934ec1a6c887a8f5 |
completed | March 8, 2026, 7:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b4e5005b18819083890de9eb985794 |
completed | March 14, 2026, 4:33 a.m. |
Created at: March 8, 2026, 3:35 p.m.