Triple
T27729116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Study Sapuri |
E697381
|
entity |
| Predicate | hasUserAccessMode |
P6865
|
FINISHED |
| Object | online only |
—
|
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: online only | Statement: [Study Sapuri, hasUserAccessMode, online only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserAccessMode Context triple: [Study Sapuri, hasUserAccessMode, online only]
-
A.
hasAccessMode
chosen
Indicates the type or method of access that one entity is permitted to use with respect to another entity or resource.
-
B.
hasUserAccessPolicy
Indicates that a specific access control policy is defined or associated for a user’s permissions or usage of a resource.
-
C.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
D.
hasAccessModel
Indicates that one entity is permitted to use, interact with, or retrieve a particular model controlled by another entity or system.
-
E.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 3:10 p.m.