Triple
T16591937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A215 road |
E403109
|
entity |
| Predicate | passesThrough |
P225
|
FINISHED |
| Object | Walworth |
E155898
|
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: Walworth | Statement: [A215 road, passesThrough, Walworth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Walworth Context triple: [A215 road, passesThrough, Walworth]
-
A.
Walworth
chosen
Walworth is a district in the London Borough of Southwark, England, known for its historic working-class roots and proximity to central London.
-
B.
Walworth
Walworth is a surname of English origin borne by various notable individuals, including American jurist Reuben H. Walworth.
-
C.
Westlands
Westlands is a prominent commercial and residential district in Nairobi known for its shopping centers, nightlife, and business hubs.
-
D.
Holworthy
Holworthy is a surname most notably associated with Sir Matthew Holworthy, a historical English figure and benefactor.
-
E.
Yorkhill
Yorkhill is a residential neighbourhood in the city of Vaughan, Ontario, known for its diverse community and proximity to Toronto.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e359a123e8819095cd73cd848a3345 |
completed | April 18, 2026, 10:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00759b9e5081909815d2cd00d44490 |
completed | May 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 5:16 a.m.