Triple
T29715722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westwick |
E751901
|
entity |
| Predicate | civilParishGroupedWith |
P168172
|
FINISHED |
| Object | Oakington |
—
|
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: Oakington | Statement: [Westwick, civilParishGroupedWith, Oakington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilParishGroupedWith Context triple: [Westwick, civilParishGroupedWith, Oakington]
-
A.
civilParishIn
Indicates that a civil parish is located within or administratively belongs to a specified larger geographic or governmental area.
-
B.
civilParishFor
Indicates that one entity is the civil parish to which another entity (such as a place or administrative area) belongs or is assigned.
-
C.
onlyCivilParishOf
Indicates that one entity is the sole civil parish associated with, or contained within, the other entity, with no other civil parishes sharing that association.
-
D.
civilParishNumber
Indicates the identifying number assigned to a specific civil parish within an administrative or geographic system.
-
E.
civilParishCouncil
Indicates that a civil parish is governed or administered by a particular parish council.
- F. None of above. chosen
Provenance (4 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 28, 2026, 7:33 p.m.