Triple
T29180829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faust Symphony |
E739739
|
entity |
| Predicate | textSourceForFinale |
P153560
|
FINISHED |
| Object | Chorus mysticus from Goethe’s Faust |
—
|
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: Chorus mysticus from Goethe’s Faust | Statement: [Faust Symphony, textSourceForFinale, Chorus mysticus from Goethe’s Faust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textSourceForFinale Context triple: [Faust Symphony, textSourceForFinale, Chorus mysticus from Goethe’s Faust]
-
A.
textSourceOfFinale
chosen
Indicates that a text serves as the narrative or conceptual source material for a work’s finale or final section.
-
B.
textSources
Indicates that one entity serves as a source or origin for the text content associated with another entity.
-
C.
originalFinale
Indicates that something serves as the initial or authentic concluding part or ending of another work, event, or sequence.
-
D.
typicalSourceText
Indicates that the related entity is a common or representative textual source from which information, examples, or data about another entity are typically drawn.
-
E.
movementTextSource
Indicates that a piece of movement-related text originates from or is derived from a specified source.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663450ba88190aaa465977605d426 |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:57 a.m.