Triple
T32854690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abschied (D 957 No. 7) |
E840343
|
entity |
| Predicate | cycleCatalogueNumber |
P165938
|
FINISHED |
| Object | D 957 |
—
|
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: D 957 | Statement: [Abschied (D 957 No. 7), cycleCatalogueNumber, D 957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cycleCatalogueNumber Context triple: [Abschied (D 957 No. 7), cycleCatalogueNumber, D 957]
-
A.
catalogueNumberOfCycle
chosen
Indicates that an entity is assigned a specific catalogue number identifying a particular cycle within a cataloging system.
-
B.
workCatalogueNumber
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
-
C.
keyCatalogueNumber
Indicates the catalog or reference number assigned to a key within a key collection or inventory system.
-
D.
catalogueRaisonneNumber
Indicates the identifier assigned to a work in a catalogue raisonné, linking it to its authoritative scholarly listing.
-
E.
chronNumber
Indicates that one entity is assigned a specific chronological number or position in an ordered sequence relative to others.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 1:17 a.m.