Triple
T26887146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanopy |
E677072
|
entity |
| Predicate | primaryAccessModel |
P6529
|
FINISHED |
| Object | public libraries |
—
|
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: public libraries | Statement: [Kanopy, primaryAccessModel, public libraries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAccessModel Context triple: [Kanopy, primaryAccessModel, public libraries]
-
A.
primaryAccessPolicy
Indicates the main rule or set of rules that governs how access to a resource or system is granted, restricted, or managed.
-
B.
secondaryAccessMode
Indicates an additional, non-primary way in which an entity can be accessed, used, or interacted with.
-
C.
primaryAccessPoint
Indicates that one entity serves as the main or principal point through which another entity is accessed or entered.
-
D.
primaryAEWModel
Indicates that an entity serves as the main or designated primary airborne early warning (AEW) model associated with another entity.
-
E.
accessMode
chosen
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: April 27, 2026, 5:42 a.m.