Triple
T37358221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O zittre nicht, mein lieber Sohn |
E927510
|
entity |
| Predicate | opusOrCatalogNumber |
P10579
|
FINISHED |
| Object | K. 620 |
—
|
NE NERFINISHED |
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: K. 620 | Statement: [O zittre nicht, mein lieber Sohn, opusOrCatalogNumber, K. 620]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opusOrCatalogNumber Context triple: [O zittre nicht, mein lieber Sohn, opusOrCatalogNumber, K. 620]
-
A.
holotypeSpecimenNumber
Indicates the identifying specimen number assigned to the holotype that formally defines a taxon in biological classification.
-
B.
catalogNumberDDO
Indicates the identifier or catalog number assigned to an item within the DDO cataloging or documentation system.
-
C.
cataloguedWith
Indicates that an item has been recorded, classified, or registered using a particular cataloging system, method, or identifier.
-
D.
namedTaxon
Indicates that an entity is identified as, or associated with, a particular taxonomic name.
-
E.
opusNumber
chosen
Indicates that a creative work is assigned a specific opus number identifying its place within a creator’s catalog or chronological sequence of works.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.