Triple
T2714163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coursera Plus |
E59928
|
entity |
| Predicate | accessScope |
P42519
|
FINISHED |
| Object | large catalog of Coursera content |
—
|
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: large catalog of Coursera content | Statement: [Coursera Plus, accessScope, large catalog of Coursera content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessScope Context triple: [Coursera Plus, accessScope, large catalog of Coursera content]
-
A.
accessRestriction
Indicates a limitation or control placed on who or what can access a particular resource, location, or information.
-
B.
accessRole
Indicates the specific permissions or level of authority an entity has when accessing another entity or resource.
-
C.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
D.
accessMode
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
-
E.
accessRestrictedTo
Indicates that access to a resource, location, or information is limited exclusively to a specified entity or group under defined conditions.
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda93a2388190b55a1c821ef6bc64 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8abcc348190bfa05c0abc4bcee7 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:55 p.m.