Triple
T23902156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodong |
E601074
|
entity |
| Predicate | controlledMediaSystem |
P14447
|
FINISHED |
| Object | North Korean state media |
—
|
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: North Korean state media | Statement: [Rodong, controlledMediaSystem, North Korean state media]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledMediaSystem Context triple: [Rodong, controlledMediaSystem, North Korean state media]
-
A.
mediaControl
chosen
Indicates a relationship where one entity directs, regulates, or influences the creation, distribution, or content of media controlled by another entity.
-
B.
controlMedium
Indicates that an entity regulates, directs, or influences another entity through a particular medium or channel.
-
C.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
D.
mediaControlProtocol
Indicates a protocol or method used to control the playback, routing, or management of media content between devices or systems.
-
E.
startOfMediaControl
Indicates the point in time or event at which a media control action (such as play, pause, or seek) is initiated.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cddf46948190b8625811725fe41d |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.