Triple
T4086005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OECD Internal Audit |
E87585
|
entity |
| Predicate | followsGuidance |
P12723
|
FINISHED |
| Object | Institute of Internal Auditors guidance |
—
|
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: Institute of Internal Auditors guidance | Statement: [OECD Internal Audit, followsGuidance, Institute of Internal Auditors guidance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsGuidance Context triple: [OECD Internal Audit, followsGuidance, Institute of Internal Auditors guidance]
-
A.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
B.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
-
C.
guidedBy
chosen
Indicates that an entity’s actions, decisions, or movement are directed, advised, or led by another entity.
-
D.
hasGuidelineCount
Indicates the number of guidelines associated with or applicable to a given entity.
-
E.
indicatesComplianceWith
Indicates that one entity conforms to, satisfies, or adheres to the rules, standards, or requirements specified by another entity or framework.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc7b7cc4819089cfbf2b1c23ccc5 |
completed | March 9, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.