Triple
T2584478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lichfield District Council |
E57165
|
entity |
| Predicate | hasLeaderAndCabinetModel |
P40521
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lichfield District Council, hasLeaderAndCabinetModel, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeaderAndCabinetModel Context triple: [Lichfield District Council, hasLeaderAndCabinetModel, true]
-
A.
hasCouncilLeaderModel
Indicates that an entity is associated with a specific model or representation of its council leader.
-
B.
hasCabinet
Indicates that one entity possesses, includes, or is equipped with a cabinet associated with it.
-
C.
hasLeader
Indicates that one entity serves as the leader or head of another entity.
-
D.
hasParliamentaryLeader
Indicates that a political party or parliamentary group is associated with a specific individual who serves as its leader within a parliamentary body.
-
E.
hasCabinetCollectiveResponsibility
Indicates that members of a cabinet are collectively responsible for decisions and policies, sharing accountability and presenting a unified position.
- F. None of above. chosen
Provenance (4 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3cb33a08190a3eae1a95e1b63bf |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd37ef248819090ab6b86b67e355f |
completed | March 7, 2026, 7:27 a.m. |
Created at: March 6, 2026, 9:49 p.m.