Triple
T7539093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Mary the Virgin Church, Kemsing |
E178226
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Kemsing |
E178226
|
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: Kemsing | Statement: [St Mary the Virgin Church, Kemsing, locatedIn, Kemsing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kemsing Context triple: [St Mary the Virgin Church, Kemsing, locatedIn, Kemsing]
-
A.
Kemsing
chosen
Kemsing is a village and civil parish in the Sevenoaks District of Kent, England, known for its rural character and location near the North Downs.
-
B.
Jemgum
Jemgum is a small municipality in the East Frisian region of Lower Saxony in northwestern Germany, known for its rural landscape along the Ems River.
-
C.
Balkum
Balkum is a residential suburb located in the Thane region of Maharashtra, India.
-
D.
Kesbewa
Kesbewa is a suburban town in Sri Lanka’s Western Province, situated within the greater Colombo metropolitan area.
-
E.
Kaming
Kaming is a town in Austria that is twinned as a sister city with Queenstown, New Zealand.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f87280f0819097d4ffc2e1b62cf8 |
completed | March 27, 2026, 9:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c856b687708190a1fe1351be70616b |
completed | March 28, 2026, 10:31 p.m. |
Created at: March 27, 2026, 3:48 p.m.