Triple
T20846068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surrey |
E513228
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Ewell |
—
|
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: Ewell | Statement: [Surrey, contains, Ewell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ewell Context triple: [Surrey, contains, Ewell]
-
A.
Ewell
chosen
Ewell is a suburban town in the borough of Epsom and Ewell in Surrey, England, known for its historic village center and proximity to London.
-
B.
Ewell
Ewell is a small, remote waterfront community on Smith Island in the Chesapeake Bay, known for its crabbing heritage and traditional island culture.
-
C.
Lorton
Lorton is a small village and civil parish in Cumbria, England, situated in the scenic Lake District near the town of Cockermouth.
-
D.
Lorton
Lorton is a suburban community in Fairfax County, Northern Virginia, known for its residential neighborhoods, proximity to major transportation routes, and redevelopment of the former Lorton Reformatory site.
-
E.
Ludwell
Ludwell is an English-origin surname historically associated with colonial Virginia families and figures such as Hannah Harrison Ludwell.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c34ec254819082610264c7af20c8 |
completed | April 21, 2026, 12:22 a.m. |
Created at: April 16, 2026, 12:43 p.m.