Triple
T16327332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | España, Op. 165 |
E396454
|
entity |
| Predicate | catalogueNumberType |
P24430
|
FINISHED |
| Object | opus number |
—
|
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: opus number | Statement: [España, Op. 165, catalogueNumberType, opus number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueNumberType Context triple: [España, Op. 165, catalogueNumberType, opus number]
-
A.
catalogueType
chosen
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
B.
workCatalogueNumber
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
-
C.
catalogueRaisonneNumber
Indicates the identifier assigned to a work in a catalogue raisonné, linking it to its authoritative scholarly listing.
-
D.
categoryNumbering
Indicates that items within a category are assigned an ordered or structured numbering scheme that defines their position or sequence in that category.
-
E.
catalogueSystem
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4dcd034819081d849003d918245 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:07 a.m.