Triple
T23871947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortuna Imperatrix Mundi |
E592750
|
entity |
| Predicate | closingMovementOf |
P45404
|
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, closingMovementOf, Carmina Burana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closingMovementOf Context triple: [Fortuna Imperatrix Mundi, closingMovementOf, Carmina Burana]
-
A.
closingMovement
Indicates a movement in which one entity reduces distance or space relative to another, bringing them closer together.
-
B.
closingMovementCharacter
Indicates a characteristic or quality of the movement involved in closing something (e.g., how the closing action is performed or behaves).
-
C.
closingPosition
Indicates that an entity terminates, finalizes, or brings to an end the position or state of another entity.
-
D.
closingForm
chosen
Indicates that one entity serves as the closing or concluding form, version, or configuration of another entity or process.
-
E.
closingLocation
Indicates the place or venue where an event, process, or activity comes to an end or is formally concluded.
- 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.