Triple
T15859170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 해병대특수수색대 |
E384536
|
entity |
| Predicate | partOf |
P40
|
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: [해병대특수수색대, partOf, 대한민국 해병대]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 대한민국 해병대 Context triple: [해병대특수수색대, partOf, 대한민국 해병대]
-
A.
대한민국 해병대
chosen
대한민국 해병대는 상륙작전과 신속 대응 임무를 주 임무로 하는 대한민국 국군의 해병 전투 병과이다.
-
B.
제2해병사단
제2해병사단은 대한민국 해병대 예하에서 서해 및 수도권 방어를 주임무로 하는 상륙·기동 중심의 전투 사단이다.
-
C.
Republic of Korea 9th Infantry Division
The Republic of Korea 9th Infantry Division is a South Korean Army formation renowned for its fierce defensive actions during the Korean War, particularly in major engagements against Chinese forces.
-
D.
제1해병사단
제1해병사단은 상륙작전과 기동전 수행을 주 임무로 하는 대한민국 해병대의 핵심 전력 사단이다.
-
E.
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.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1555956ec8190b13602a177e7a2bb |
completed | April 16, 2026, 9:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa941a0a481909c8d8e98861b46d6 |
completed | May 9, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.