Triple
T34199173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of Glasgow |
E877323
|
entity |
| Predicate | hasLibraryResources |
P79099
|
FINISHED |
| Object | theological texts |
—
|
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: theological texts | Statement: [University of Glasgow, hasLibraryResources, theological texts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLibraryResources Context triple: [University of Glasgow, hasLibraryResources, theological texts]
-
A.
hasLibraries
Indicates that an entity possesses, contains, or is associated with one or more libraries.
-
B.
hasLibraryHoldings
chosen
Indicates that a library possesses or maintains specific items or collections within its holdings.
-
C.
hasLibraryBranch
Indicates that an entity possesses or is associated with one or more library branches as part of its organizational structure or services.
-
D.
hasDigitalLibrary
Indicates that an entity maintains or provides access to a collection of digital resources or publications.
-
E.
hasLibraryDistrict
Indicates that an entity is associated with or falls within the jurisdiction of a particular library district.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: May 1, 2026, 1:55 a.m.