Triple
T28207808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammer horror films |
E717078
|
entity |
| Predicate | distributionRegions |
P158838
|
FINISHED |
| Object | United Kingdom |
—
|
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: United Kingdom | Statement: [Hammer horror films, distributionRegions, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributionRegions Context triple: [Hammer horror films, distributionRegions, United Kingdom]
-
A.
distributionRegionsInclude
chosen
Indicates that certain geographic or market regions are encompassed within the overall distribution coverage of a product or service.
-
B.
catalogRegion
Indicates the geographic or organizational region associated with a given catalog or catalog entry.
-
C.
includedRegions
Indicates that certain regions are contained within, or form part of, a larger specified region or set of regions.
-
D.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
-
E.
locationRegion2
Indicates that an entity is located within, or associated with, a second or alternative geographic or administrative region.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 10:36 p.m.