Triple
T18911299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telemadrid headquarters |
E462612
|
entity |
| Predicate | scopeOfBroadcast |
P8301
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Telemadrid headquarters, scopeOfBroadcast, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfBroadcast Context triple: [Telemadrid headquarters, scopeOfBroadcast, regional]
-
A.
hasBroadcastScope
chosen
Indicates that a broadcast is intended to reach a specified scope or range of recipients, areas, or contexts.
-
B.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
C.
broadcastFor
Indicates that one entity transmits or disseminates content, information, or a signal on behalf of, or in service of, another entity.
-
D.
scopeOfRecipients
Indicates the range or group of recipients to whom something (such as information, communication, or benefits) is directed or applicable.
-
E.
broadcastContext
Indicates that an entity disseminates information, content, or signals to multiple recipients within a particular situational or environmental setting.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c6226f4081909b77aac26c574980 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.