Triple
T15859072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 제1해병사단 |
E384533
|
entity |
| Predicate | 지휘체계 |
P15789
|
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: [제1해병사단, 지휘체계, 국방부 직할 해병대사령부 예하]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 지휘체계 Context triple: [제1해병사단, 지휘체계, 국방부 직할 해병대사령부 예하]
-
A.
militarySystem
chosen
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
-
B.
warSecretary
Indicates that one entity serves as the war secretary (or secretary of war/defense) of another entity, typically a government or state.
-
C.
militaryDoctrine
Indicates that one entity embodies, follows, or defines the strategic military principles, tactics, and operational guidelines used by another entity.
-
D.
tacticalSystem
Indicates a relationship where an entity functions as or is associated with a tactical system used for planning, coordinating, or executing tactical operations.
-
E.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
- 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.