Triple
T23871816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O Fortuna |
E592746
|
entity |
| Predicate | isFamousExcerptOf |
P154265
|
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: [O Fortuna, isFamousExcerptOf, Carmina Burana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFamousExcerptOf Context triple: [O Fortuna, isFamousExcerptOf, Carmina Burana]
-
A.
famousIndividual
Indicates that an individual is widely known and recognized by a large number of people, typically for notable achievements, status, or public visibility.
-
B.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
C.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
-
D.
famousWriterAssociated
Indicates a relationship where a well-known or renowned writer is connected or linked to a particular entity (such as a work, place, event, or organization).
-
E.
notableAuthorMention
Indicates that a notable or well-known author is referenced or cited in relation to the subject.
- 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.