Triple
T34785777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borough of Stevenage |
E1002799
|
entity |
| Predicate | hasElectoralWardType |
P73599
|
FINISHED |
| Object | borough 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: borough ward | Statement: [Borough of Stevenage, hasElectoralWardType, borough ward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectoralWardType Context triple: [Borough of Stevenage, hasElectoralWardType, borough ward]
-
A.
hasElectoralWardStatus
Indicates that an entity holds the official status or designation of an electoral ward within an administrative or political system.
-
B.
municipalWardType
chosen
Indicates the specific category or classification of a municipal ward within a local government or administrative structure.
-
C.
hasElectoralRollType
Indicates the specific category or type of electoral roll associated with an entity, such as general, special, or supplementary voter lists.
-
D.
electoralDistrictType
Indicates the specific category or kind of electoral district associated with an entity (e.g., federal, state, local).
-
E.
hasWardAssembly
Indicates that a specified ward is associated with a particular assembly or representative governing body.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 3:59 p.m.