Triple
T31129554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian press |
E793460
|
entity |
| Predicate | hasPublicServiceBroadcaster |
P16302
|
FINISHED |
| Object | NRK |
—
|
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: NRK | Statement: [Norwegian press, hasPublicServiceBroadcaster, NRK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicServiceBroadcaster Context triple: [Norwegian press, hasPublicServiceBroadcaster, NRK]
-
A.
hasBroadcastService
Indicates that an entity provides or is associated with a particular broadcast service.
-
B.
hasBroadcaster
chosen
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
-
C.
hasBroadcastingFacility
Indicates that an entity possesses or operates a facility used for broadcasting signals or content.
-
D.
hasBroadcastFeature
Indicates that an entity includes or supports a broadcast-related capability or functionality.
-
E.
hasBroadcastRegulator
Indicates that one entity serves as the broadcast regulatory authority or body responsible for overseeing or controlling the broadcasting activities of another entity.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 29, 2026, 9:05 p.m.