Triple
T9147467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Gravesham |
E219492
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Meopham |
E781113
|
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: Meopham | Statement: [Borough of Gravesham, contains, Meopham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Meopham Context triple: [Borough of Gravesham, contains, Meopham]
-
A.
Meopham
chosen
Meopham is a large rural village and civil parish in north-west Kent, England, known for its historic buildings, green spaces, and traditional village character.
-
B.
Thrupp
Thrupp is a small canal-side village in Oxfordshire, England, known for its historic wharf and picturesque setting along the Oxford Canal.
-
C.
Peacham
Peacham is a small historic town in Vermont known for its rural New England character and scenic landscapes.
-
D.
Westmere
Westmere is Intel's 32 nm microarchitecture, a die-shrink of Nehalem that introduced several new features and performance improvements to the Core processor lineup.
-
E.
Tealby
Tealby is a picturesque rural village in eastern England, known for its traditional stone cottages and scenic setting within the Lincolnshire countryside.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca918a3c881909c34a6a682eb2625 |
completed | April 1, 2026, 5:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d05458ac188190acc47fc99f8ee182 |
completed | April 3, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:20 p.m.