Triple
T8461949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allington Lock |
E200061
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Allington |
E109054
|
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: Allington | Statement: [Allington Lock, locatedIn, Allington]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Allington Context triple: [Allington Lock, locatedIn, Allington]
-
A.
Allington
chosen
Allington is an English village best known in literature as the rural setting of Anthony Trollope’s novel "The Small House at Allington."
-
B.
Allerton
Allerton is an English surname historically associated with early colonial figures such as Mayflower passenger Isaac Allerton.
-
C.
Allerton
Allerton is a coastal village neighborhood within the town of Hull, Massachusetts, known for its residential seaside setting on Boston’s South Shore.
-
D.
Allerton
Allerton is a residential neighborhood in the northeast Bronx, New York City, characterized by its diverse community and mix of apartment buildings and one- to two-family homes.
-
E.
Allerton
Allerton is a suburban residential area of Liverpool, England, known for its leafy streets, parks, and mix of schools and local amenities.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4a0ff4c8190b17bbd33db632cea |
completed | March 31, 2026, 3:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce1df5d76881909ea5040824985cc3 |
completed | April 2, 2026, 7:42 a.m. |
Created at: March 30, 2026, 6:10 p.m.