Triple
T24628402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC North project |
E609603
|
entity |
| Predicate | keySiteType |
P109097
|
FINISHED |
| Object | broadcasting centre |
—
|
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: broadcasting centre | Statement: [BBC North project, keySiteType, broadcasting centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keySiteType Context triple: [BBC North project, keySiteType, broadcasting centre]
-
A.
notableSiteType
Indicates that a site is notable specifically for being of a particular type or category (e.g., a notable example of that kind of site).
-
B.
keyExecutionSite
Indicates the location or context in which a key (e.g., cryptographic or access key) is actually used or executed.
-
C.
significantPlaceType
chosen
Indicates the type or category of place that holds particular significance in relation to the subject.
-
D.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
E.
keyLandingSite
Indicates a location that serves as the primary or designated site where something (such as a vehicle, object, or mission) is intended to land or touch down.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:32 a.m.