Triple
T681895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MicroMasters programs |
E13199
|
entity |
| Predicate | credentialFormat |
P130
|
FINISHED |
| Object | digital certificate |
—
|
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: digital certificate | Statement: [MicroMasters programs, credentialFormat, digital certificate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: credentialFormat Context triple: [MicroMasters programs, credentialFormat, digital certificate]
-
A.
credentialType
Indicates the specific kind or category of credential associated with an entity or relationship.
-
B.
standardFormBasedIn
Indicates that a standardized form or format is established, defined, or grounded in a particular source, basis, or reference framework.
-
C.
formOfRecognition
Indicates a relationship where one entity serves as an official acknowledgment, honor, or validation granted to another entity.
-
D.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
E.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a06f9ee88190a2d757aacd8e3f5b |
completed | March 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69a49d1d79608190a849ba9ffad2879d |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.