Triple
T2519919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commission on Audit |
E55497
|
entity |
| Predicate | scopeOfAudit |
P14568
|
FINISHED |
| Object | national government agencies |
—
|
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: national government agencies | Statement: [Commission on Audit, scopeOfAudit, national government agencies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfAudit Context triple: [Commission on Audit, scopeOfAudit, national government agencies]
-
A.
oversightScope
Indicates the range or extent of responsibilities and activities that fall under an entity’s oversight or supervisory authority.
-
B.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
C.
coverageScope
chosen
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
D.
typeOfAudit
Indicates the specific category or kind of audit being performed or referenced in relation to an entity.
-
E.
scopeOfContribution
Indicates the specific area, domain, or extent within which an entity’s contribution or involvement applies.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd2343e3081908819dc58d8ff40ce |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.