Triple
T4039569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westminster City Council |
E83911
|
entity |
| Predicate | usesSystemOf |
P32380
|
FINISHED |
| Object | leader and cabinet executive |
—
|
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: leader and cabinet executive | Statement: [Westminster City Council, usesSystemOf, leader and cabinet executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSystemOf Context triple: [Westminster City Council, usesSystemOf, leader and cabinet executive]
-
A.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
B.
usesCaseSystem
Indicates that one entity employs or operates using a particular case system (e.g., grammatical or structural case-marking system).
-
C.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
D.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
E.
associatedSystem
chosen
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
- 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_69aed92f7cf0819098e0539bdcc3767f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb37e24c81908d6357ab8ba5388d |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.