Triple
T26075109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee on Budgetary Control |
E657658
|
entity |
| Predicate | procedureInvolvement |
P75671
|
FINISHED |
| Object | budget discharge procedure |
—
|
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 discharge procedure | Statement: [Committee on Budgetary Control, procedureInvolvement, budget discharge procedure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: procedureInvolvement Context triple: [Committee on Budgetary Control, procedureInvolvement, budget discharge procedure]
-
A.
procedureArea
Indicates the physical or conceptual area in which a procedure is performed or applies.
-
B.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
-
C.
involvedLocation
Indicates that an event, action, or relationship takes place in, or is significantly associated with, a particular location.
-
D.
procedureFeature
Indicates that a procedure possesses, involves, or is characterized by a particular feature or attribute.
-
E.
concernsProcedure
chosen
Indicates that something is about, related to, or involves a particular procedure.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 7:33 p.m.