Triple
T824522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwigslied |
E17824
|
entity |
| Predicate | approximateCompositionYear |
P13262
|
FINISHED |
| Object | 881 |
—
|
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: 881 | Statement: [Ludwigslied, approximateCompositionYear, 881]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCompositionYear Context triple: [Ludwigslied, approximateCompositionYear, 881]
-
A.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
B.
estimatedYearOfCreation
chosen
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
C.
compositionYear
Indicates the year in which a work (such as a piece of music, art, or literature) was originally created or composed.
-
D.
commissionedYear
Indicates the year in which something (typically a work, project, or item) was formally ordered, authorized, or put into production.
-
E.
discoveryYear
Indicates the calendar year in which something was first discovered or identified.
- 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab7eb0a08190889463edb0e7bd59 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa781e1081909df006f730296c53 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.