Triple
T232625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Senate Budget and Fiscal Review Committee |
E4439
|
entity |
| Predicate | documentTypeReviewed |
P1394
|
FINISHED |
| Object | budget bills |
—
|
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: budget bills | Statement: [California State Senate Budget and Fiscal Review Committee, documentTypeReviewed, budget bills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentTypeReviewed Context triple: [California State Senate Budget and Fiscal Review Committee, documentTypeReviewed, budget bills]
-
A.
reviewedBy
chosen
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
B.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
C.
issuedDocument
Indicates that one entity has formally created and provided an official document to another entity.
-
D.
documentNumber
Indicates the unique identifying number assigned to a specific document in the relationship.
-
E.
usedDocument
Indicates that one entity has employed, referenced, or otherwise made use of a particular document in performing an action or fulfilling a purpose.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f14f72081908182e76300b59358 |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b5c8c888190b5544e687736b373 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.