Triple
T5970546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kimilsungism–Kimjongilism |
E132859
|
entity |
| Predicate | claimsToContinue |
P66818
|
FINISHED |
| Object | revolutionary cause of Juche |
—
|
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: revolutionary cause of Juche | Statement: [Kimilsungism–Kimjongilism, claimsToContinue, revolutionary cause of Juche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsToContinue Context triple: [Kimilsungism–Kimjongilism, claimsToContinue, revolutionary cause of Juche]
-
A.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
B.
claimsToMark
Indicates that one entity asserts or alleges that it has marked, labeled, or designated another entity in some specified way.
-
C.
claimsToFollow
Indicates that one entity asserts or professes adherence to the principles, rules, or leadership of another entity.
-
D.
claimsToModify
Indicates that one entity asserts it can change, alter, or adjust another entity or its properties.
-
E.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
- F. None of above. chosen
Provenance (4 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03e174c7c8190b04113f6529f5f0e |
completed | March 22, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69c0335b55a48190927a5b1529edb542 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c03e16476481908361fbb3049664e9 |
completed | March 22, 2026, 7:08 p.m. |
Created at: March 22, 2026, 4:03 p.m.