Triple
T29027543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In der Fremde (second song) |
E737633
|
entity |
| Predicate | cycleOpus |
P170675
|
FINISHED |
| Object | Op. 39 |
—
|
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: Op. 39 | Statement: [In der Fremde (second song), cycleOpus, Op. 39]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cycleOpus Context triple: [In der Fremde (second song), cycleOpus, Op. 39]
-
A.
opensCycle
Indicates that an action or event initiates or begins a recurring sequence or cyclical process.
-
B.
cycleBy
Indicates that one entity moves or travels by means of riding a bicycle (or similar cycle) in relation to another entity or context.
-
C.
cycleWith
Indicates that two or more entities participate together in a cycling activity, such as riding bicycles along the same route or at the same time.
-
D.
cycleTheme
Indicates a recurring subject, motif, or pattern that repeatedly appears or is developed across parts of a work, process, or sequence.
-
E.
cycleCentralTopic
Indicates that a topic serves as the main or focal subject around which a particular cycle or recurring process is organized.
- 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 28, 2026, 9:53 a.m.