Triple
T7038632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gooi |
E163449
|
entity |
| Predicate | mediaCenter |
P74683
|
FINISHED |
| Object | Hilversum |
—
|
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: Hilversum | Statement: [Gooi, mediaCenter, Hilversum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaCenter Context triple: [Gooi, mediaCenter, Hilversum]
-
A.
mediaFocus
Indicates that the primary attention, coverage, or emphasis of a media source is directed toward a particular entity or topic.
-
B.
mediaCovered
Indicates that one entity (such as a media outlet or source) has reported on, featured, or otherwise provided coverage of another entity or event.
-
C.
mediaAssociation
Indicates a relationship where one media item is linked, connected, or otherwise associated with another entity or media resource.
-
D.
mediaExposure
Indicates the extent to which an entity is subjected to or receives attention from media channels such as television, radio, print, or online platforms.
-
E.
mediaConsumption
Indicates the act or pattern of engaging with, using, or experiencing media content (such as watching, listening, or reading).
- F. None of above. chosen
Provenance (4 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_69c6885e7c1c8190be32a8f79ab4e0cf |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bb602081908bfa6186a1f5a4b4 |
completed | March 27, 2026, 7:59 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:36 p.m.