Triple
T10039539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieder eines fahrenden Gesellen |
E205258
|
entity |
| Predicate | orchestrationYear |
P68149
|
FINISHED |
| Object | 1893 |
—
|
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: 1893 | Statement: [Lieder eines fahrenden Gesellen, orchestrationYear, 1893]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orchestrationYear Context triple: [Lieder eines fahrenden Gesellen, orchestrationYear, 1893]
-
A.
orchestrationDate
Indicates the date on which the orchestration (coordination or arrangement of related actions or processes) occurs or is scheduled to occur.
-
B.
yearOrchestrated
chosen
Indicates the specific year in which a musical work was orchestrated or arranged for orchestra.
-
C.
orchestration
Indicates the coordination and arrangement of multiple components or processes to work together harmoniously toward a unified outcome.
-
D.
orchestrationIncludes
Indicates that one orchestration contains, incorporates, or makes use of another orchestration as part of its overall structure or process.
-
E.
musicArrangedYear
Indicates the year in which a piece of music was arranged or re-arranged into its specific version.
- 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_69ca834f70e88190b2d74828b7767ec1 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcee186708190bc9fecd637b4f7e6 |
completed | April 2, 2026, 2:05 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.