Triple

T15859120
Position Surface form Disambiguated ID Type / Status
Subject 제9해병여단 E384534 entity
Predicate 국가안보상역할 P45870 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. militaryPolicy
    Indicates a relationship where an entity defines, adopts, or is governed by rules, strategies, or doctrines concerning military organization, operations, or conduct.
  • B. militaryCooperation
    Indicates a collaborative relationship in which entities coordinate, support, or jointly conduct military activities, operations, or planning.
  • C. governmentalRole
    Indicates that an entity holds or is assigned a specific official position, function, or authority within a government or public administration structure.
  • D. hasPeacekeepingRole
    Indicates that an entity holds a responsibility or function related to maintaining or enforcing peace, often in a conflict or post-conflict context.
  • E. militaryResponsibility chosen
    Indicates that an entity holds authority, duty, or accountability for military actions, operations, or forces in relation to another entity.
  • 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.