Triple
T11492983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purfleet-on-Thames |
E272460
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | Purfleet |
E545743
|
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: Purfleet | Statement: [Purfleet-on-Thames, formerName, Purfleet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Purfleet Context triple: [Purfleet-on-Thames, formerName, Purfleet]
-
A.
Purfleet
chosen
Purfleet is a town in Essex, England, historically significant as a military and industrial riverside settlement on the River Thames.
-
B.
BENFLEET
Benfleet is a town in Essex, England, situated near the Thames Estuary and forming part of the commuter belt for London.
-
C.
Fleetwood Harbour
Fleetwood Harbour is a coastal port and fishing harbour in the town of Fleetwood, Lancashire, England, serving commercial, fishing, and leisure vessels.
-
D.
Hythe
Hythe is a historic coastal town in Kent, England, known as one of the original Cinque Ports that once played a key role in maritime defense and trade.
-
E.
Hythe
Hythe is a small village in northwestern Alberta, Canada, situated west of the city of Grande Prairie.
- 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a21fb048190acb0960aefd4fe0a |
completed | April 10, 2026, 2:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6047d95548190b445aa3b4f1e71cc |
completed | April 20, 2026, 10:48 a.m. |
Created at: April 8, 2026, 9:36 p.m.