Triple
T15859075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 제1해병사단 |
E384533
|
entity |
| Predicate | 임무특성 |
P23258
|
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.
missionCharacteristic
chosen
Indicates that a mission possesses a specific attribute, feature, or quality that characterizes its nature or execution.
-
B.
militaryCharacteristic
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or context.
-
C.
squadCharacteristic
Indicates that a particular characteristic, trait, or property is attributed to a squad as a whole.
-
D.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
E.
battleCharacteristic
Indicates a relationship where a specific trait, quality, or feature is attributed to a battle or combat scenario.
- 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.