Triple
T33598580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summerdown Comprehensive School |
E860644
|
entity |
| Predicate | productionLocationOfDepiction |
P24427
|
FINISHED |
| Object | Bristol |
—
|
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: Bristol | Statement: [Summerdown Comprehensive School, productionLocationOfDepiction, Bristol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionLocationOfDepiction Context triple: [Summerdown Comprehensive School, productionLocationOfDepiction, Bristol]
-
A.
isProducedIn
Indicates that something is created, manufactured, or generated within a particular place, context, or process.
-
B.
placeOfDepiction
chosen
Indicates the location or setting where the depicted subject is shown as being situated in the representation.
-
C.
productionCompanyLocation
Indicates the relationship between a production company and the geographic location where it is based or operates.
-
D.
firstProductionPlace
Indicates the location where something was originally or first produced.
-
E.
basedInFictionalWorkLocation
Indicates that an entity’s location or setting is situated within a fictional place as depicted in a specific creative work.
- 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 1, 2026, 1:41 a.m.