Triple
T24988297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paddock Wood Library |
E625377
|
entity |
| Predicate | providesDigitalAccess |
P35796
|
FINISHED |
| Object | e‑books |
—
|
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: e‑books | Statement: [Paddock Wood Library, providesDigitalAccess, e‑books]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesDigitalAccess Context triple: [Paddock Wood Library, providesDigitalAccess, e‑books]
-
A.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
B.
hasDigitalService
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
-
C.
offersDigitalBorrowingThrough
Indicates that one entity provides access to borrow digital items or content via another entity or platform.
-
D.
hasDigitalLibraryServices
chosen
Indicates that an entity provides or supports access to digital library-related services or resources.
-
E.
digitalProvider
Indicates that one entity serves as the supplier or source of digital services, content, or infrastructure for another 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:03 a.m.