Triple
T12733164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somerville College Library |
E304292
|
entity |
| Predicate | catalogueAccess |
P106623
|
FINISHED |
| Object | online library catalogue |
—
|
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: online library catalogue | Statement: [Somerville College Library, catalogueAccess, online library catalogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueAccess Context triple: [Somerville College Library, catalogueAccess, online library catalogue]
-
A.
catalogueFor
Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
-
B.
catalogueSystem
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
-
C.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
D.
catalogueEntry
Indicates that an item is recorded as an entry within a catalogue or organized listing.
-
E.
cataloguePrefix
Indicates that one entity serves as the initial or leading segment of another entity’s catalogue identifier or listing code.
- F. None of above. chosen
Provenance (4 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:26 p.m.