Triple
T23871805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O Fortuna |
E592746
|
entity |
| Predicate | dynamicProfile |
P154264
|
FINISHED |
| Object | extreme contrasts in dynamics |
—
|
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: extreme contrasts in dynamics | Statement: [O Fortuna, dynamicProfile, extreme contrasts in dynamics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynamicProfile Context triple: [O Fortuna, dynamicProfile, extreme contrasts in dynamics]
-
A.
dynamicCharacter
Indicates that a character undergoes significant internal change or development over the course of a narrative.
-
B.
dynamicFeatures
Indicates that an entity possesses or supports features whose presence, behavior, or configuration can change at runtime or in response to varying conditions.
-
C.
usesProfile
Indicates that one entity employs, operates under, or is associated with a particular profile in performing its actions or functions.
-
D.
participantProfile
Indicates that an entity serves as the profile or descriptive record associated with a particular participant in an event, activity, or process.
-
E.
dynamicShape
Indicates that an entity’s shape changes over time or in response to certain conditions or interactions.
- 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_69f1cbfe1f948190ad2c0d5bbe0c7240 |
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.