Triple
T32196528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AICP Certification Exam |
E822416
|
entity |
| Predicate | credentialAbbreviation |
P173316
|
FINISHED |
| Object | AICP |
—
|
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: AICP | Statement: [AICP Certification Exam, credentialAbbreviation, AICP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: credentialAbbreviation Context triple: [AICP Certification Exam, credentialAbbreviation, AICP]
-
A.
credentialName
Indicates the specific title or label assigned to a credential associated with an entity.
-
B.
abbreviationOfUser
Indicates that one entity is an abbreviated or shortened form of another entity associated with a user.
-
C.
ownerAbbreviation
Indicates that one entity is an abbreviated or shortened form of the name or designation of another entity that owns or is primarily associated with it.
-
D.
bearerShortName
Indicates that an entity serves as the short or abbreviated name used to identify the bearer in the context of a relationship or action.
-
E.
credentialType
Indicates the specific kind or category of credential associated with an entity or relationship.
- F. None of above. chosen
Provenance (4 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb38af6c819082ad0dacc7acf54e |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b42902a081909126c7322858a2b3 |
completed | May 3, 2026, 2:34 a.m. |
Created at: May 1, 2026, 12:36 a.m.