Triple
T20776836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budget and Management Committee |
E511375
|
entity |
| Predicate | maySet |
P78663
|
FINISHED |
| Object | budget guidelines |
—
|
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 guidelines | Statement: [Budget and Management Committee, maySet, budget guidelines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySet Context triple: [Budget and Management Committee, maySet, budget guidelines]
-
A.
mayDefine
chosen
Indicates that one entity has the authority or capability to specify, establish, or determine the form, content, or rules of another entity.
-
B.
mayGrant
Indicates that one entity has the authority or permission to confer, assign, or bestow a right, privilege, or resource to another entity.
-
C.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
D.
mayRemove
Indicates that one entity is permitted or authorized to remove another entity or its association.
-
E.
mayAdapt
Indicates that one entity is permitted or allowed to modify, adjust, or alter another entity.
- 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_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c26bbe108190bb7c3e5b416e44fe |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:37 p.m.