Triple
T8468974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dichterliebe, Op. 48 |
E200233
|
entity |
| Predicate | compositionDecade |
P46731
|
FINISHED |
| Object | 1840s |
—
|
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: 1840s | Statement: [Dichterliebe, Op. 48, compositionDecade, 1840s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compositionDecade Context triple: [Dichterliebe, Op. 48, compositionDecade, 1840s]
-
A.
decadeList
Indicates that an entity is associated with a list of decades, typically representing time periods relevant to that entity.
-
B.
productionDecade
chosen
Indicates the decade during which something (such as a work, product, or item) was produced or created.
-
C.
decade
Indicates that the relationship or event is associated with, occurs within, or is characteristic of a specific ten-year time period.
-
D.
decadeContext
Indicates that the relationship or fact is specifically situated within, or pertains to, a particular decade as its temporal context.
-
E.
builtInDecade
Indicates that a structure or object was constructed during a specific decade.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d5dd088190a79050417f527f14 |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.