Triple
T31198656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South East Cambridgeshire |
E795400
|
entity |
| Predicate | containsPartOfDistrict |
P192490
|
FINISHED |
| Object | South Cambridgeshire |
—
|
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: South Cambridgeshire | Statement: [South East Cambridgeshire, containsPartOfDistrict, South Cambridgeshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPartOfDistrict Context triple: [South East Cambridgeshire, containsPartOfDistrict, South Cambridgeshire]
-
A.
hasDistrictPart
chosen
Indicates that one administrative or geographic entity includes another entity as a district-level subdivision or component.
-
B.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
-
C.
isInnerDistrictOf
Indicates that one district is geographically or administratively located within and subordinate to another, larger district.
-
D.
occursInDistrict
Indicates that an event or activity takes place within the boundaries of a specific district.
-
E.
centerIsPartOfDistrict
Indicates that a specific center is located within and belongs administratively to a particular district.
- F. None of above.
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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
Created at: April 29, 2026, 9:09 p.m.