Triple
T17017553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBC broadcasting facilities (historical main site) |
E412861
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | broadcasting facility complex |
C35530
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: broadcasting facility complex Context triple: [MBC broadcasting facilities (historical main site), instanceOf, broadcasting facility complex]
-
A.
television studio complex
A television studio complex is a purpose-built facility that houses multiple studios, control rooms, production offices, technical infrastructure, and support spaces for creating, recording, and broadcasting television content.
-
B.
broadcasting headquarters
A broadcasting headquarters is a central facility where television, radio, and digital media content is produced, managed, and transmitted to audiences across various distribution channels.
-
C.
broadcasting building
chosen
A broadcasting building is a specialized facility equipped with studios, control rooms, transmission systems, and support infrastructure for producing and distributing radio, television, or digital media content.
-
D.
broadcast control facility
A broadcast control facility is a centralized location equipped with the systems and personnel needed to manage, monitor, and direct the transmission and routing of broadcast audio and video content.
-
E.
broadcast television station
A broadcast television station is a facility that produces, assembles, and transmits television programming over the airwaves to be received by the general public within a designated coverage area.
- F. None of above.
Provenance (1 batch)
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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:33 a.m.