Triple
T6409380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Korean political system |
E127666
|
entity |
| Predicate | rulingPartyFounded |
P13446
|
FINISHED |
| Object | 1949 |
—
|
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: 1949 | Statement: [North Korean political system, rulingPartyFounded, 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingPartyFounded Context triple: [North Korean political system, rulingPartyFounded, 1949]
-
A.
politicalPartyFounded
Indicates that an entity (typically a person or group) established or created a political party.
-
B.
startTimeAsRulingParty
chosen
Indicates the point in time when an entity begins its tenure or role as the ruling party.
-
C.
foundingParties
Indicates the entities that jointly establish or create an organization, institution, or agreement as its original founders.
-
D.
governingSince
Indicates that one entity has held a governing or ruling role over another entity starting from a specified point in time.
-
E.
historicalDominantParties
Indicates that certain political parties have historically held dominant or ruling positions within a given political system or jurisdiction.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068cdf25881908d42a5d979637ad6 |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:41 p.m.