Triple
T8927665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle City Council |
E212575
|
entity |
| Predicate | canOverrideMayorVeto |
P37504
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Seattle City Council, canOverrideMayorVeto, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canOverrideMayorVeto Context triple: [Seattle City Council, canOverrideMayorVeto, yes]
-
A.
vetoOverrideBy
Indicates that a decision or law previously vetoed by one authority is subsequently overridden and enacted by another authority with sufficient power.
-
B.
vetoOverridden
chosen
Indicates that a previously issued veto has been nullified or reversed by a sufficient overriding authority or vote.
-
C.
vetoOverrideChamber
Indicates the legislative chamber that has the authority or took action to override a veto.
-
D.
canOverrideSenateInSomeCases
Indicates that an entity has the authority to overrule or bypass the decisions or actions of a senate under certain specified conditions or circumstances.
-
E.
vetoOverrideRequirement
Indicates the conditions or threshold (such as a required majority) needed for a legislative body to override an executive veto.
- 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_69ca8395c438819087d7cb844ab5990c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6672af10819084a6e50f0302f732 |
completed | April 1, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed3286c8190a21de2ee11f2639f |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:57 p.m.