Triple
T31129552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian press |
E793460
|
entity |
| Predicate | hasMajorBroadcaster |
P147821
|
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, hasMajorBroadcaster, NRK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorBroadcaster Context triple: [Norwegian press, hasMajorBroadcaster, NRK]
-
A.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
-
B.
hasBroadcastingFacility
Indicates that an entity possesses or operates a facility used for broadcasting signals or content.
-
C.
majorCommercialBroadcaster
Indicates that an entity operates as a primary, large-scale commercial television or radio broadcasting organization within a media market.
-
D.
majorBroadcastNetworksPresent
chosen
Indicates that one or more major broadcast television networks are present or represented in the given context or location.
-
E.
hasRadioBroadcasts
Indicates that one entity transmits or provides content via radio broadcasts to another entity or audience.
- 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_69fffbb5d0188190b6d168de8626ff68 |
completed | May 10, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69fffa3bc1208190a277961385a4789f |
completed | May 10, 2026, 3:23 a.m. |
Created at: April 29, 2026, 9:05 p.m.