Triple
T9750545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Board of Regents of the University of Nebraska |
E236428
|
entity |
| Predicate | hasGoverningRole |
P90489
|
FINISHED |
| Object | budget approval |
—
|
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 approval | Statement: [Board of Regents of the University of Nebraska, hasGoverningRole, budget approval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoverningRole Context triple: [Board of Regents of the University of Nebraska, hasGoverningRole, budget approval]
-
A.
governsRoleOf
Indicates that one entity has authority or control over the role, responsibilities, or functions assigned to another entity.
-
B.
hasLocalGovernanceRole
Indicates that an entity holds an official position or responsibility within a local or municipal governing body.
-
C.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
D.
hasOrganizationalRole
Indicates that an entity holds a specific role, position, or function within an organization.
-
E.
governingBodySupportRole
Indicates that one entity plays a supporting or auxiliary role in relation to the governing body 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_69ca84d4eddc8190996fec1417d2bae8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f6bb4088190ab8d52ef61d24bee |
completed | April 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:24 p.m.