Triple
T22142898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Dorset District Council |
E547209
|
entity |
| Predicate | hasGovernmentOfficeCategory |
P130835
|
FINISHED |
| Object | local authority |
—
|
LITERAL 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: local authority | Statement: [West Dorset District Council, hasGovernmentOfficeCategory, local authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentOfficeCategory Context triple: [West Dorset District Council, hasGovernmentOfficeCategory, local authority]
-
A.
basedInGovernmentType
Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
-
B.
hasGovernmentalBodyType
chosen
Indicates the specific kind or classification of governmental body that an entity possesses or is associated with.
-
C.
hasOffice
Indicates that an entity possesses or maintains an office at a particular location or within a specific organization.
-
D.
hasOfficeType
Indicates that an entity’s office is classified as a specific type or category of office.
-
E.
isPartOfGovernment
Indicates that an entity belongs to, is included within, or functions as a component of a governmental body or system.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129bf78108190b50d937917258693 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.