Triple
T11212635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prittlewell Priory |
E265346
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Prittlewell |
E440424
|
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: Prittlewell | Statement: [Prittlewell Priory, locatedIn, Prittlewell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prittlewell Context triple: [Prittlewell Priory, locatedIn, Prittlewell]
-
A.
Prittlewell
chosen
Prittlewell is a suburban area of Southend-on-Sea in Essex, England, known for its historic roots and residential character.
-
B.
Epping
Epping is a market town in the Epping Forest district of Essex, England, known for its historic high street and proximity to the ancient Epping Forest.
-
C.
Epping
Epping is a suburb in Melbourne, Australia, known for its residential communities, shopping facilities, and role as a transport hub in the city's northern corridor.
-
D.
Benfleet
Benfleet is a town in the borough of Castle Point in Essex, England, known as a residential commuter area with historical roots dating back to Saxon times.
-
E.
Ockendon
Ockendon is a settlement in the borough of Thurrock in Essex, England, known for its suburban character and proximity to London.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d7f47c8190b78c640ff1a01943 |
completed | April 9, 2026, 5:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e497569efc8190b8e9cb6b1db3f94d |
completed | April 19, 2026, 8:50 a.m. |
Created at: April 8, 2026, 9:30 p.m.