Triple
T15859124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 제9해병여단 |
E384534
|
entity |
| Predicate | 지휘통제 |
P1061
|
FINISHED |
| Object | 대한민국 해병대사령부의 작전통제 하에 있음 |
—
|
LITERAL 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: [제9해병여단, 지휘통제, 대한민국 해병대사령부의 작전통제 하에 있음]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 지휘통제 Context triple: [제9해병여단, 지휘통제, 대한민국 해병대사령부의 작전통제 하에 있음]
-
A.
strategicCommand
Indicates that one entity issues high-level, overarching directives or plans that guide the actions or decisions of another entity.
-
B.
commander
chosen
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
C.
jointOperationsCommander
Indicates that one entity serves as the commander responsible for overseeing joint operations involving multiple forces or organizations in relation to another entity.
-
D.
sideCommander
Indicates that an entity serves as the commanding officer or leader in charge of a particular side or faction in a conflict, operation, or organization.
-
E.
warSecretary
Indicates that one entity serves as the war secretary (or secretary of war/defense) of another entity, typically a government or state.
- F. None of above.
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_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:50 a.m.