Triple
T6915271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobham Bridge |
E160033
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Cobham village centre |
E140975
|
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: Cobham village centre | Statement: [Cobham Bridge, near, Cobham village centre]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cobham village centre Context triple: [Cobham Bridge, near, Cobham village centre]
-
A.
Cobham
chosen
Cobham is a village in Surrey, England, known for its affluent residential character, proximity to London, and scenic riverside setting.
-
B.
Cobham
Cobham is a clan associated with the Efik people, an ethnic group primarily found in southeastern Nigeria.
-
C.
Foxhall Village
Foxhall Village is a historic, primarily residential neighborhood in Northwest Washington, D.C., known for its Tudor-style homes and tree-lined streets.
-
D.
Chobham
Chobham is a village and civil parish in Surrey, England, known for its rural character, common land, and historic buildings.
-
E.
Coleham
Coleham is a suburb of Shrewsbury, England, situated just south of the town centre on the east bank of the River Severn.
- 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_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9dec058819094d1913a1e5218c0 |
completed | March 27, 2026, 7:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7491589c08190982a84f2b61b497b |
completed | March 28, 2026, 3:20 a.m. |
Created at: March 27, 2026, 2:26 p.m.