Triple
T23871967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortuna Imperatrix Mundi |
E592750
|
entity |
| Predicate | workNumberWithinCantata |
P154266
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Fortuna Imperatrix Mundi, workNumberWithinCantata, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberWithinCantata Context triple: [Fortuna Imperatrix Mundi, workNumberWithinCantata, 1]
-
A.
workNumberInBWV
Indicates that a musical work is identified by a specific catalog number within the Bach-Werke-Verzeichnis (BWV) catalog.
-
B.
workNumberInComposerChamberMusic
Indicates that a specific work number is assigned to a composer's piece within their body of chamber music.
-
C.
workNumberWithinOratorio
Indicates that a specific work is identified by its numerical position within an oratorio.
-
D.
numberOfCantatas
Indicates the quantity of cantatas associated with a given entity.
-
E.
estimatedNumberOfCantatas
Indicates the approximate or inferred count of cantatas associated with an entity.
- F. None of above. chosen
Provenance (4 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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cbfed81881909905f71377f759b1 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:14 p.m.