Triple
T19944200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Korean economy |
E479380
|
entity |
| Predicate | chronicIssues |
P122526
|
FINISHED |
| Object | low productivity |
—
|
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: low productivity | Statement: [North Korean economy, chronicIssues, low productivity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronicIssues Context triple: [North Korean economy, chronicIssues, low productivity]
-
A.
longTermIssue
chosen
Indicates a problem, condition, or concern that persists over an extended period rather than being short-lived or temporary.
-
B.
clinicalCondition
Indicates that one entity has, exhibits, or is associated with a particular medical or health-related condition described by the other entity.
-
C.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
-
D.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
-
E.
settingOfIllness
Indicates the context, environment, or circumstances in which an illness occurs or manifests.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a64b2788190a49c4ed40aa93b98 |
completed | April 20, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.