Triple
T31011693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wyoming State Auditor’s Office |
E790223
|
entity |
| Predicate | typeOfAuditing |
P9164
|
FINISHED |
| Object | government financial auditing |
—
|
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: government financial auditing | Statement: [Wyoming State Auditor’s Office, typeOfAuditing, government financial auditing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAuditing Context triple: [Wyoming State Auditor’s Office, typeOfAuditing, government financial auditing]
-
A.
typeOfAudit
chosen
Indicates the specific category or kind of audit being performed or referenced in relation to an entity.
-
B.
typeOfVetting
Indicates the specific kind or category of vetting process that is applied to an entity or relationship.
-
C.
numberOfAuditoria
Indicates the total count of auditoria associated with or contained within a given entity.
-
D.
hasAuditor
Indicates that an entity is formally examined, reviewed, or verified by a designated auditor.
-
E.
auditFunctionExercisedThrough
Indicates that an audit function is carried out, implemented, or realized by means of a specified mechanism, process, or intermediary.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
Created at: April 29, 2026, 8:57 p.m.