Triple
T27754012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 김대중 |
E701289
|
entity |
| Predicate | 주요정책 |
P63712
|
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.
majorPolicy
chosen
Indicates a relationship where a policy is classified as a primary or highly significant guiding rule or course of action within a system or organization.
-
B.
nationalPolicy
Indicates that an entity establishes, embodies, or is governed by an official policy at the level of a nation-state.
-
C.
policyTopic
Indicates that one entity is about, concerned with, or categorized under a particular policy-related subject or theme.
-
D.
policyFocus
Indicates that an entity (such as a person, organization, or document) is primarily concerned with, directed toward, or centered on a particular policy area or issue.
-
E.
economicPolicyWing
Indicates a relationship where an entity functions as the economic policy division or unit within a larger organization or structure.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 4:22 p.m.