Triple
T11581203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DZBB-TV |
E274628
|
entity |
| Predicate | broadcastAreaType |
P2441
|
FINISHED |
| Object | terrestrial television |
—
|
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: terrestrial television | Statement: [DZBB-TV, broadcastAreaType, terrestrial television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastAreaType Context triple: [DZBB-TV, broadcastAreaType, terrestrial television]
-
A.
broadcastType
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
-
B.
broadcastRegion
chosen
Indicates the geographic area or market in which content is transmitted or made available for broadcast.
-
C.
broadcastBand
Indicates that something is transmitted over a particular broadcast frequency band (e.g., AM, FM, VHF, UHF) for distribution to receivers.
-
D.
broadcastRole
Indicates that an entity has a specific role or function within a broadcast or transmission context.
-
E.
broadcastVia
Indicates that an action, message, or content is transmitted or disseminated through a specified medium, channel, or platform.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8904c51b881909e7be84c6f3de79f |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.