Triple
T20377677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neasden Temple |
E497736
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Neasden |
—
|
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: Neasden | Statement: [Neasden Temple, locatedIn, Neasden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neasden Context triple: [Neasden Temple, locatedIn, Neasden]
-
A.
Neasden
chosen
Neasden is a suburban area in northwest London, England, known for its residential character and proximity to major roads and rail links.
-
B.
Cheshunt
Cheshunt is a town in Hertfordshire, England, situated just north of London and known as a commuter hub with rail links into the capital.
-
C.
Hoddlesden
Hoddlesden is a small village in Lancashire, England, situated in a rural valley setting and historically associated with textile manufacturing.
-
D.
Kelvedon
Kelvedon is a village and civil parish in Essex, England, known for its historic High Street and role as a commuter settlement with rail links to London.
-
E.
Bennetts End
Bennetts End is a residential area and suburb located within the county of Hertfordshire in England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678ae3468819087d7db7e1b79efc7 |
completed | April 20, 2026, 7:04 p.m. |
Created at: April 16, 2026, 11:27 a.m.