Triple
T36351987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Garrison Pub |
E895229
|
entity |
| Predicate | settingCityInSeries |
P7747
|
FINISHED |
| Object | Small Heath, Birmingham |
—
|
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: Small Heath, Birmingham | Statement: [The Garrison Pub, settingCityInSeries, Small Heath, Birmingham]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingCityInSeries Context triple: [The Garrison Pub, settingCityInSeries, Small Heath, Birmingham]
-
A.
cityOfSeries
Indicates the city in which a series is primarily set, based, or associated.
-
B.
settingCity
chosen
Indicates that a work or event takes place in, or is primarily located within, a particular city.
-
C.
basedInSeriesSetting
Indicates that something (such as a work, event, or element) is situated within or occurs in the primary setting established by a particular series.
-
D.
seriesLocation
Indicates that one entity is the place or venue where a series (such as events, performances, or installments) takes place.
-
E.
situatedInSeries
Indicates that one entity is located or positioned within a particular series, sequence, or ordered collection of related items.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:09 p.m.