Triple
T10277578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harling Road |
E241007
|
entity |
| Predicate | nearbySettlement |
P350
|
FINISHED |
| Object | East Harling |
E281752
|
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: East Harling | Statement: [Harling Road, nearbySettlement, East Harling]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: East Harling Context triple: [Harling Road, nearbySettlement, East Harling]
-
A.
East Harling
chosen
East Harling is a village and civil parish in Norfolk, England, known for its historic church and rural setting within the Breckland area.
-
B.
Leasingham
Leasingham is a small village and civil parish in the South Kesteven district of Lincolnshire, England.
-
C.
Prittlewell
Prittlewell is a suburban area of Southend-on-Sea in Essex, England, known for its historic roots and residential character.
-
D.
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.
-
E.
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.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d29f0cf08190a2c5e7523d5c731e |
completed | April 7, 2026, 9:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d71cf7f644819085dd687b286004ad |
completed | April 9, 2026, 3:28 a.m. |
Created at: April 6, 2026, 11:37 a.m.