Triple
T38691824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest Heath district |
E949285
|
entity |
| Predicate | hadParishCouncil |
P21036
|
FINISHED |
| Object | Mildenhall Parish Council |
—
|
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: Mildenhall Parish Council | Statement: [Forest Heath district, hadParishCouncil, Mildenhall Parish Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadParishCouncil Context triple: [Forest Heath district, hadParishCouncil, Mildenhall Parish Council]
-
A.
hasParishCouncils
chosen
Indicates that an entity possesses, is served by, or is administratively associated with one or more parish councils.
-
B.
civilParishCouncil
Indicates that a civil parish is governed or administered by a particular parish council.
-
C.
hasCountyCouncil
Indicates that an entity is administratively governed or overseen by a specific county council.
-
D.
hasParishHouse
Indicates that a church or parish entity possesses or is associated with a specific parish house building.
-
E.
hasParishCommunity
Indicates that an entity is associated with, served by, or belongs to a specific parish community.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.