Triple
T17891584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stratton St Margaret |
E447328
|
entity |
| Predicate | hasNeighbourhood |
P4813
|
FINISHED |
| Object | Covingham |
—
|
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: Covingham | Statement: [Stratton St Margaret, hasNeighbourhood, Covingham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Covingham Context triple: [Stratton St Margaret, hasNeighbourhood, Covingham]
-
A.
Covingham
chosen
Covingham is a residential parish and suburb on the eastern side of Swindon in Wiltshire, England.
-
B.
Cavenham
Cavenham is a small rural village and civil parish in Suffolk, England, known for its surrounding heathland and agricultural landscape.
-
C.
Cullingworth
Cullingworth is a village in West Yorkshire, England, situated near the town of Bingley and within commuting distance of Bradford.
-
D.
Finglesham
Finglesham is a small village in Kent, England, known for its Anglo-Saxon archaeological finds and rural setting near the town of Deal.
-
E.
Cudham
Cudham is a historic rural village in southeast England, known for its traditional character and countryside setting within Greater London.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7948888190b59ddc7061d13e84 |
completed | April 19, 2026, 9:16 a.m. |
Created at: April 10, 2026, 10:19 a.m.