Triple
T32756861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Ballroom Balcony |
E837647
|
entity |
| Predicate | withinBuilding |
P166606
|
FINISHED |
| Object | Winter Gardens Blackpool complex |
—
|
NE NERFINISHED |
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: Winter Gardens Blackpool complex | Statement: [Empress Ballroom Balcony, withinBuilding, Winter Gardens Blackpool complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinBuilding Context triple: [Empress Ballroom Balcony, withinBuilding, Winter Gardens Blackpool complex]
-
A.
occursInBuilding
Indicates that an event or activity takes place within a specific building.
-
B.
locatedInBuildingWithFeature
Indicates that something is located in a building that possesses a specified feature or characteristic.
-
C.
isLocatedInBuilding
chosen
Indicates that one entity is physically situated within or inside the structure of a particular building.
-
D.
locatedInSectionOfBuilding
Indicates that one entity is situated within a specific section or area of a building.
-
E.
hostedInBuilding
Indicates that an event, activity, or service takes place within or is accommodated inside a specific building.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:12 a.m.