Triple
T32742434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Der Abschied |
E837251
|
entity |
| Predicate | textCollectionSource |
P175043
|
FINISHED |
| Object | Die chinesische Flöte |
—
|
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: Die chinesische Flöte | Statement: [Der Abschied, textCollectionSource, Die chinesische Flöte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textCollectionSource Context triple: [Der Abschied, textCollectionSource, Die chinesische Flöte]
-
A.
textSources
Indicates that one entity serves as a source or origin for the text content associated with another entity.
-
B.
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.
-
C.
collectionCompiler
Indicates that an entity is responsible for compiling, assembling, or building a collection from its constituent elements or sources.
-
D.
iconographicTextSource
Indicates that a text serves as the source or basis for the content, meaning, or interpretation of an iconographic representation.
-
E.
textSourceApocrypha
Indicates that the referenced text originates from or is classified as apocryphal writings.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 1:12 a.m.