Triple
T14254369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EBSCOhost |
E353348
|
entity |
| Predicate | accessProvidedThrough |
P51771
|
FINISHED |
| Object | academic 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: academic libraries | Statement: [EBSCOhost, accessProvidedThrough, academic libraries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessProvidedThrough Context triple: [EBSCOhost, accessProvidedThrough, academic libraries]
-
A.
accessProvides
chosen
Indicates that one entity grants or enables the ability to use, enter, or retrieve another entity or resource.
-
B.
accessedThrough
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
C.
accessDeterminedBy
Indicates that the ability to access a resource is governed or controlled by a specified condition, rule, or authority.
-
D.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
E.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6297f38c819090d7c7fd8bfa2e9e |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:09 a.m.