Triple
T33264757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biblioteca Digital Hispánica |
E851613
|
entity |
| Predicate | hasMetadataStandard |
P153446
|
FINISHED |
| Object | library cataloging standards |
—
|
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: library cataloging standards | Statement: [Biblioteca Digital Hispánica, hasMetadataStandard, library cataloging standards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMetadataStandard Context triple: [Biblioteca Digital Hispánica, hasMetadataStandard, library cataloging standards]
-
A.
hasStandardizationLevel
Indicates the degree or extent to which something conforms to an established standard or set of standardized criteria.
-
B.
hasAssociatedStandard
chosen
Indicates that something is linked to or governed by a particular standard or set of standards.
-
C.
hasStandardVersion
Indicates that one entity serves as the official or canonical version of another entity.
-
D.
hasStandardizationBody
Indicates that an entity is associated with, governed by, or defined by a specific standards-setting organization or authority.
-
E.
isStandardizedAcross
Indicates that something maintains a consistent, uniform form, method, or specification across multiple instances, contexts, or locations.
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:32 a.m.