Triple
T15970359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 해병대사령부 |
E387302
|
entity |
| Predicate | 책임 |
P636
|
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: [해병대사령부, 책임, 해병대 전투준비태세 유지]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 책임 Context triple: [해병대사령부, 책임, 해병대 전투준비태세 유지]
-
A.
responsibleFor
chosen
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
B.
accountabilityTo
Indicates that one entity is responsible for explaining, justifying, or answering for its actions, decisions, or outcomes to another entity.
-
C.
commitment
Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
-
D.
obligation
Indicates that one entity is bound or required to perform a duty, action, or fulfill a condition toward another entity or according to a rule or agreement.
-
E.
recallLiability
Indicates a relationship where an entity bears legal or financial responsibility for initiating or managing a product recall.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.