Triple
T22070250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlisle City Council |
E545386
|
entity |
| Predicate | hadElectedCouncillors |
P115983
|
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: [Carlisle City Council, hadElectedCouncillors, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadElectedCouncillors Context triple: [Carlisle City Council, hadElectedCouncillors, true]
-
A.
hadElectedCouncil
chosen
Indicates that an entity was governed or administered by a council whose members were chosen through an election process.
-
B.
hasCouncillors
Indicates that an entity is associated with one or more councillors who serve or represent it in an official capacity.
-
C.
membersElected
Indicates that certain individuals are chosen through an election process to serve as members of a group, body, or organization.
-
D.
electsCouncillorsTo
Indicates a relationship where one entity selects or chooses individuals to serve as councillors in another entity or governing body.
-
E.
electedMembers
Indicates that certain individuals have been chosen through an election process to serve as members of a specific body or organization.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128881af481909b28cda2d343f4e3 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.