Triple
T6409400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Korean political system |
E127666
|
entity |
| Predicate | freedomOfReligion |
P7601
|
FINISHED |
| Object | tightly controlled |
—
|
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: tightly controlled | Statement: [North Korean political system, freedomOfReligion, tightly controlled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freedomOfReligion Context triple: [North Korean political system, freedomOfReligion, tightly controlled]
-
A.
religionPolicy
chosen
Indicates the stance, rules, or approach an entity adopts toward religious beliefs, practices, or institutions.
-
B.
religiousAffiliation
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
C.
declaredReligion
Indicates that an entity has formally stated or reported a particular religious affiliation.
-
D.
officialReligion
Indicates that a particular religion is formally recognized and designated as the official or state religion of an entity (such as a country or region).
-
E.
religiousClaim
Indicates that an entity asserts, expresses, or is associated with a statement or belief grounded in religion or spiritual doctrine.
- 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.