Triple
T33678835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokdu Janggun |
E862836
|
entity |
| Predicate | hasRoleOfReferent |
P4342
|
FINISHED |
| Object | leader of the Donghak Peasant Revolution |
—
|
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: leader of the Donghak Peasant Revolution | Statement: [Nokdu Janggun, hasRoleOfReferent, leader of the Donghak Peasant Revolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleOfReferent Context triple: [Nokdu Janggun, hasRoleOfReferent, leader of the Donghak Peasant Revolution]
-
A.
refersToRole
chosen
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
-
B.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
C.
hasReferralRole
Indicates that an entity participates in a referral relationship by holding a specific role within that referral.
-
D.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
E.
hasSubjectRoleIn
Indicates that an entity serves in a specific subject role within a particular context, situation, or relationship.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 1, 2026, 1:43 a.m.