Triple
T23871946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortuna Imperatrix Mundi |
E592750
|
entity |
| Predicate | openingMovementOf |
P83469
|
FINISHED |
| Object | Carmina Burana |
—
|
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: Carmina Burana | Statement: [Fortuna Imperatrix Mundi, openingMovementOf, Carmina Burana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingMovementOf Context triple: [Fortuna Imperatrix Mundi, openingMovementOf, Carmina Burana]
-
A.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
B.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
-
C.
openingDynamic
Indicates that one entity initiates or begins another entity or process in a way that can change or vary over time or context.
-
D.
hasOpeningMovement
chosen
Indicates that a work, performance, or sequence includes a distinct initial movement or section that begins the overall piece.
-
E.
openingMovementCharacter
Indicates the characteristic or quality that defines how the opening movement of a work is expressed or perceived.
- 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_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. |
Created at: April 17, 2026, 8:14 p.m.