Triple
T15101496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rijksvoorlichtingsdienst |
E360675
|
entity |
| Predicate | usesCommunicationChannels |
P2798
|
FINISHED |
| Object | press releases |
—
|
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: press releases | Statement: [Rijksvoorlichtingsdienst, usesCommunicationChannels, press releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCommunicationChannels Context triple: [Rijksvoorlichtingsdienst, usesCommunicationChannels, press releases]
-
A.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
B.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
-
C.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
D.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
-
E.
communicationFunction
Indicates that one entity serves a communicative role or purpose in relation to another, such as conveying, mediating, or facilitating the exchange of information.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00550007481909e02ee1d597a4d37 |
completed | April 15, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.