Triple
T21997297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARABOSAI |
E543237
|
entity |
| Predicate | typeOfStandardPromoted |
P43031
|
FINISHED |
| Object | public sector auditing standards |
—
|
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: public sector auditing standards | Statement: [ARABOSAI, typeOfStandardPromoted, public sector auditing standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfStandardPromoted Context triple: [ARABOSAI, typeOfStandardPromoted, public sector auditing standards]
-
A.
standardPromoted
Indicates that something has been elevated or advanced to a recognized or officially accepted standard level.
-
B.
standardsType
chosen
Indicates the classification or category of standards that apply to or are associated with an entity or activity.
-
C.
typicalPromotionBasis
Indicates the usual criterion or set of criteria on which promotions are based within a given context.
-
D.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
E.
isPromotedAs
Indicates that one entity is advertised, marketed, or presented to others in a particular way or role by 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12765fb0c81908f7b7acda065ee2f |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:19 p.m.