Triple
T14235882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University Library of Pavia |
E352874
|
entity |
| Predicate | supportsDigitalResources |
P35796
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [University Library of Pavia, supportsDigitalResources, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDigitalResources Context triple: [University Library of Pavia, supportsDigitalResources, true]
-
A.
supportsDigitalDownloads
Indicates that one entity enables or allows the other entity to provide or access digital file downloads.
-
B.
hasDigitalLibraryServices
chosen
Indicates that an entity provides or supports access to digital library-related services or resources.
-
C.
hasDigitalLibrary
Indicates that an entity maintains or provides access to a collection of digital resources or publications.
-
D.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
E.
hasDigitalCollections
Indicates that an entity possesses or provides access to one or more collections of materials in digital form.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62411c888190a154acd56fe3fcaf |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:07 a.m.