Triple
T8082440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maughan Library |
E188648
|
entity |
| Predicate | hasDigitalServices |
P10738
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Maughan Library, hasDigitalServices, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalServices Context triple: [Maughan Library, hasDigitalServices, yes]
-
A.
hasDigitalService
chosen
Indicates that an entity provides, offers, or is associated with a service delivered through digital or online means.
-
B.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
C.
hasDigitalSystem
Indicates that an entity possesses, uses, or is equipped with a digital system (such as software, hardware, or an integrated digital platform).
-
D.
hasDigitalInitiative
Indicates that an entity is engaged in or associated with a specific digital project, program, or transformation effort.
-
E.
hasDigitalLibraryServices
Indicates that an entity provides or supports access to digital library-related services or resources.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb415cb4688190920868317e77bbff |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.