Triple
T13345681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abinger Common |
E317942
|
entity |
| Predicate | civilParish |
P2739
|
FINISHED |
| Object | Abinger |
E537995
|
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: Abinger | Statement: [Abinger Common, civilParish, Abinger]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Abinger Context triple: [Abinger Common, civilParish, Abinger]
-
A.
Abinger
chosen
Abinger is a village and civil parish in Surrey, England, known for its rural landscape and historic buildings.
-
B.
Abinger
Abinger is a small rural community located within the township of Addington Highlands in eastern Ontario, Canada.
-
C.
Abinger Hammer
Abinger Hammer is a picturesque village in Surrey, England, known for its historic water-powered clock and scenic setting within the Surrey Hills countryside.
-
D.
Abinger Common
Abinger Common is a rural village and common land area in Surrey, England, known for its woodland, heathland, and scenic walking routes in the Surrey Hills.
-
E.
Empingham
Empingham is a village in the county of Rutland in the East Midlands of England, known for its proximity to Rutland Water reservoir.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e89c65c819093f3bea11d6073c5 |
completed | April 11, 2026, 1:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f726738ea08190b0b7634b29f5d94e |
completed | May 3, 2026, 10:41 a.m. |
Created at: April 9, 2026, 9:31 p.m.