Triple
T7595068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hot Fuzz |
E179837
|
entity |
| Predicate | setting |
P1957
|
FINISHED |
| Object | Sandford |
E674779
|
NE FINISHED |
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: Sandford | Statement: [Hot Fuzz, setting, Sandford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sandford Context triple: [Hot Fuzz, setting, Sandford]
-
A.
Sandford
Sandford is the given name of Sandford Fleming, the Canadian engineer and inventor best known for proposing worldwide standard time zones.
-
B.
Sandford
chosen
Sandford is the fictional English village that serves as the primary setting of the film "Hot Fuzz."
-
C.
Stopford
Stopford refers to Lieutenant-General Sir Montagu Stopford, a British Army officer who played a key leadership role in the Burma Campaign of World War II, particularly noted for his command in the Southeast Asian theater.
-
D.
Durford
Durford is a small settlement in West Sussex, England, situated in the countryside near the River Rother.
-
E.
Wilford
Wilford is a masculine given name most notably associated with American actor Wilford Brimley.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9bbcd8081909a229d7faa2ffdc8 |
completed | March 27, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c87080c19c8190ba6a632f6f277621 |
completed | March 29, 2026, 12:21 a.m. |
Created at: March 27, 2026, 3:53 p.m.