Triple
T22513931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N4 road |
E556592
|
entity |
| Predicate | servesTown |
P847
|
FINISHED |
| Object | Enfield |
—
|
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: Enfield | Statement: [N4 road, servesTown, Enfield]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Enfield Context triple: [N4 road, servesTown, Enfield]
-
A.
Enfield
Enfield is a small rural town located in Tompkins County in the Finger Lakes region of New York State.
-
B.
Enfield
Enfield is a town in County Meath, Ireland, known as a commuter hub with rail connections on the Dublin–Sligo line.
-
C.
Enfield
chosen
Enfield is a historic town in north London that developed from a Middlesex market settlement into a major suburban and commercial center.
-
D.
Enfield
Enfield is a suburb in the inner northern region of Adelaide, South Australia, known for its residential character and proximity to the city centre.
-
E.
Woolwich
Woolwich is a district in southeast London, England, historically significant as a military and industrial hub along the River Thames.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d62bea48190aaf34aa93bb3f67b |
completed | April 29, 2026, 1:22 a.m. |
Created at: April 16, 2026, 8:50 p.m.