Triple
T37388329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Trade Hall |
E928632
|
entity |
| Predicate | replacedAsHomeOfHalléBy |
P197280
|
FINISHED |
| Object | Bridgewater Hall |
—
|
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: Bridgewater Hall | Statement: [Free Trade Hall, replacedAsHomeOfHalléBy, Bridgewater Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedAsHomeOfHalléBy Context triple: [Free Trade Hall, replacedAsHomeOfHalléBy, Bridgewater Hall]
-
A.
reopenedAsConcertHall
Indicates that a previously closed or differently purposed venue has been opened again specifically to function as a concert hall.
-
B.
replacedInCorridorBy
Indicates that one entity has been substituted or superseded by another entity specifically within a corridor context.
-
C.
reopenedAsConservatoryIn
Indicates that something previously closed was opened again specifically as a conservatory in a given place or time.
-
D.
isPlannedToBeReplacedAsCapitalBy
Indicates that one capital city is intended or scheduled to be superseded by another as the official capital.
-
E.
inauguratedAsConcertHall
Indicates that a building or venue was officially opened and dedicated to function as a concert hall.
- F. None of above. chosen
Provenance (4 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
| PDg | Predicate description generation | batch_69fe831ba4708190a5564afd7d5a4319 |
completed | May 9, 2026, 12:43 a.m. |
Created at: May 3, 2026, 4:16 p.m.