Triple
T28222152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CMA Canada |
E711486
|
entity |
| Predicate | regulatedTitle |
P149791
|
FINISHED |
| Object | Certified Management Accountant |
—
|
NE NERFINISHED |
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: Certified Management Accountant | Statement: [CMA Canada, regulatedTitle, Certified Management Accountant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatedTitle Context triple: [CMA Canada, regulatedTitle, Certified Management Accountant]
-
A.
regulatesTitle
chosen
Indicates that one entity has the authority or function to control, govern, or set rules regarding another entity’s official title.
-
B.
creditedTitle
Indicates that a particular title or role is formally attributed to an entity as a credit.
-
C.
standardTitle
Indicates that an entity has a primary or official title or name by which it is commonly recognized.
-
D.
traditionalTitleGivenBy
Indicates that one entity has conferred or assigned a traditional or customary title to another entity.
-
E.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 27, 2026, 10:47 p.m.