Triple
T21249761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FWV 48 |
E523710
|
entity |
| Predicate | workAlternativeCatalogue |
P84753
|
FINISHED |
| Object | no standard 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: no standard opus number | Statement: [FWV 48, workAlternativeCatalogue, no standard opus number]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workAlternativeCatalogue Context triple: [FWV 48, workAlternativeCatalogue, no standard opus number]
-
A.
workCatalogueNumber
Indicates the catalog or reference number assigned to a specific work within an organized catalogue or listing.
-
B.
catalogueFor
Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
-
C.
alternateVersionOccupation
Indicates that an entity holds a particular occupation in an alternate version, timeline, or continuity compared to its primary or original depiction.
-
D.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
-
E.
alternativeCatalogNumber
chosen
Indicates that an entity is associated with an additional or substitute catalog number different from its primary catalog identifier.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359c7a648190b4345336ac3be024 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:56 p.m.