Triple
T674087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenLearning |
E13040
|
entity |
| Predicate | supportsCredentialType |
P6396
|
FINISHED |
| Object | certificates of completion |
—
|
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: certificates of completion | Statement: [OpenLearning, supportsCredentialType, certificates of completion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCredentialType Context triple: [OpenLearning, supportsCredentialType, certificates of completion]
-
A.
supportsAccountType
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
-
B.
credentialType
chosen
Indicates the specific kind or category of credential associated with an entity or relationship.
-
C.
supportsClaim
Indicates that one entity provides evidence, reasoning, or backing that strengthens or validates the truth or credibility of another entity’s claim.
-
D.
supportsAddressTypes
Indicates that an entity is capable of handling or working with one or more specified types of addresses.
-
E.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a1b3682c8190a9b9a454480c3446 |
completed | March 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69a49d1a16c48190af89e3b078a4957e |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.