Triple
T21198540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standing Committee on Estimates |
E522388
|
entity |
| Predicate | estimatesReviewed |
P143524
|
FINISHED |
| Object | operating expenditures |
—
|
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: operating expenditures | Statement: [Standing Committee on Estimates, estimatesReviewed, operating expenditures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatesReviewed Context triple: [Standing Committee on Estimates, estimatesReviewed, operating expenditures]
-
A.
reviewedAs
Indicates that one entity has evaluated, critiqued, or assessed another entity in a particular capacity, role, or context.
-
B.
areReviewedEvery
Indicates that one entity conducts reviews of another entity at every specified time interval or on every relevant occasion.
-
C.
reviewedBy
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
D.
reviewedFor
Indicates that one entity has examined or evaluated another entity for a specific purpose, standard, or context.
-
E.
approximateEstimation
Indicates an estimation relationship where one value or assessment is only roughly or closely, but not exactly, equal to another.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7333d6dec8190bbc66a71b31ea559 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5fa92a2448190896c022dd27511ad |
completed | April 20, 2026, 10:06 a.m. |
Created at: April 16, 2026, 3:16 p.m.