Triple
T5483803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Holland |
E123527
|
entity |
| Predicate | electoralWardType |
P15309
|
FINISHED |
| Object | district ward |
—
|
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: district ward | Statement: [South Holland, electoralWardType, district ward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralWardType Context triple: [South Holland, electoralWardType, district ward]
-
A.
electoralWardFor
Indicates that one entity serves as the electoral ward or voting district in which another entity (such as a place or address) is located or represented.
-
B.
electoralDistrictType
Indicates the specific category or kind of electoral district associated with an entity (e.g., federal, state, local).
-
C.
parliamentaryBoroughType
Indicates the specific classification or category of a parliamentary borough within a parliamentary or electoral system.
-
D.
constituencyType
chosen
Indicates the specific kind or category of electoral or representative district to which an entity belongs or refers.
-
E.
councilType
Indicates the specific kind or classification of a council that an entity is associated with or designated as.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.