Triple
T6164348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi University Library System |
E137518
|
entity |
| Predicate | catalogueSystem |
P69156
|
FINISHED |
| Object | online public access 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 public access catalogue | Statement: [Delhi University Library System, catalogueSystem, online public access catalogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueSystem Context triple: [Delhi University Library System, catalogueSystem, online public access catalogue]
-
A.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
B.
cataloguePrefix
Indicates that one entity serves as the initial or leading segment of another entity’s catalogue identifier or listing code.
-
C.
catalogueStatus
Indicates the current state or condition of an item within a catalogue or listing system (e.g., active, inactive, pending).
-
D.
catalog
Indicates the action of systematically listing, organizing, or recording items or information into a structured collection or database.
-
E.
catalogueEntry
Indicates that an item is recorded as an entry within a catalogue or organized listing.
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d6036f88190a4bf540e7fe8d48d |
completed | March 22, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:17 p.m.