Triple
T5995112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chepstow Town Council |
E133447
|
entity |
| Predicate | hasGovernmentBodyType |
P9175
|
FINISHED |
| Object | elected council |
—
|
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: elected council | Statement: [Chepstow Town Council, hasGovernmentBodyType, elected council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentBodyType Context triple: [Chepstow Town Council, hasGovernmentBodyType, elected council]
-
A.
hasGovernmentBody
Indicates that one entity serves as the official governing or administrative body responsible for overseeing or managing another entity.
-
B.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
-
C.
governmentBodyType
chosen
Indicates the classification or category of a governmental organization based on its structural or functional role.
-
D.
hasGovernmentTypeCountry
Indicates that a country possesses or is characterized by a particular form or type of government.
-
E.
basedInGovernmentType
Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e943dcc8190a09817e8ef0e4188 |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.