Triple
T23398169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Leader |
E559420
|
entity |
| Predicate | mostNotablyRefersTo |
P112157
|
FINISHED |
| Object | Kim Il-sung |
—
|
NE NERFINISHED |
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: Kim Il-sung | Statement: [Great Leader, mostNotablyRefersTo, Kim Il-sung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostNotablyRefersTo Context triple: [Great Leader, mostNotablyRefersTo, Kim Il-sung]
-
A.
notablyRefersTo
chosen
Indicates that one entity makes a particularly significant or noteworthy reference to another entity, beyond a routine or incidental mention.
-
B.
oftenRefersTo
Indicates that one entity is frequently used to mention, denote, or reference another entity in common usage or context.
-
C.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
D.
alsoRefersTo
Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
-
E.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
- 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_69e24549610c8190a069d6411ce5f661 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a4dd05cc81908c1e91974ffccf21 |
completed | April 29, 2026, 6:27 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:37 p.m.