Triple
T7912908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chobham Common |
E183742
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Chobham |
E183742
|
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: Chobham | Statement: [Chobham Common, locatedIn, Chobham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chobham Context triple: [Chobham Common, locatedIn, Chobham]
-
A.
Chobham
chosen
Chobham is a village and civil parish in Surrey, England, known for its rural character, common land, and historic buildings.
-
B.
Cobham
Cobham is a village in Surrey, England, known for its affluent residential character, proximity to London, and scenic riverside setting.
-
C.
Cobham
Cobham is a clan associated with the Efik people, an ethnic group primarily found in southeastern Nigeria.
-
D.
Harmondsworth
Harmondsworth is a village in the London Borough of Hillingdon, England, known for its historic Great Barn and proximity to Heathrow Airport.
-
E.
Beckenham
Beckenham is a suburban town in southeast London known for its residential character, green spaces, and commuter links into central London.
- 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a7383cc819084eab19799209d2e |
completed | March 31, 2026, 3:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc936b4d088190bfcfd3bc6c05f7e8 |
completed | April 1, 2026, 3:39 a.m. |
Created at: March 30, 2026, 5:04 p.m.