Triple
T11636292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAOL |
E276527
|
entity |
| Predicate | onlineAccessType |
P32027
|
FINISHED |
| Object | free to use |
—
|
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: free to use | Statement: [SAOL, onlineAccessType, free to use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onlineAccessType Context triple: [SAOL, onlineAccessType, free to use]
-
A.
typeOfAccess
Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
-
B.
accessibleOn
Indicates that one entity can be reached, used, or obtained through another entity (such as a platform, device, or medium).
-
C.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
D.
accessProtocol
Indicates the method or rules by which one entity is allowed to access or communicate with another entity or resource.
-
E.
accessStatus
chosen
Indicates the current level or state of permission or availability for accessing a resource or entity.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a25d80208190b33e95db2e7cc276 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.