Triple
T26703044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theed power generator complex |
E673211
|
entity |
| Predicate | filmingLocationForSet |
P4373
|
FINISHED |
| Object | Leavesden Studios |
—
|
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: Leavesden Studios | Statement: [Theed power generator complex, filmingLocationForSet, Leavesden Studios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmingLocationForSet Context triple: [Theed power generator complex, filmingLocationForSet, Leavesden Studios]
-
A.
filmingLocationContext
Indicates the contextual relationship specifying where the filming of an event, scene, or production took place.
-
B.
formerFilmingLocation
Indicates that a place was once used as a filming location for a work but is no longer used for that purpose.
-
C.
filmingLocationPattern
Indicates the typical or recurring geographic pattern of locations where filming for a production takes place.
-
D.
filmingLocationForAdaptation
Indicates the place where an adaptation (such as a film or TV version of a work) was shot or recorded.
-
E.
filmLocationFor
chosen
Indicates a relationship where a specific place serves as the filming location for a particular film or production.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6178140788190b8492b75a2eb7cc4 |
completed | May 2, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:32 a.m.