Triple
T5057390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington State Senate |
E113935
|
entity |
| Predicate | allowsPublicHearings |
P60917
|
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: [Washington State Senate, allowsPublicHearings, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsPublicHearings Context triple: [Washington State Senate, allowsPublicHearings, yes]
-
A.
heldPublicHearings
Indicates that formal meetings open to the public were conducted to gather input, discuss issues, or present information.
-
B.
paroleHearings
Indicates that one or more formal hearings are held to evaluate an incarcerated individual's eligibility or suitability for parole.
-
C.
hearsAppealsBy
Indicates that one party has the authority or role to review and decide on appeals submitted by another party.
-
D.
legislativeAudience
Indicates that the subject is the intended legislative body or group of lawmakers to whom a proposal, document, or action is directed.
-
E.
openedToPublicBy
Indicates that an entity was made accessible or available to the general public through the action or decision of another entity.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7450312881908d4e3576ca65f7fb |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:38 p.m.