Triple
T3941825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europaturm |
E92049
|
entity |
| Predicate | hasBroadcastingRange |
P8301
|
FINISHED |
| Object | covers large parts of Hesse |
—
|
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: covers large parts of Hesse | Statement: [Europaturm, hasBroadcastingRange, covers large parts of Hesse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBroadcastingRange Context triple: [Europaturm, hasBroadcastingRange, covers large parts of Hesse]
-
A.
hasBroadcastScope
chosen
Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
-
B.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
C.
hasBroadcastFeature
Indicates that an entity includes or supports a broadcast-related capability or functionality.
-
D.
hasBroadcastService
Indicates that an entity provides or is associated with a particular broadcast service.
-
E.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.