Triple
T32742243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans Bethge |
E837246
|
entity |
| Predicate | workUsedAsTextFor |
P42407
|
FINISHED |
| Object | Das Lied von der Erde |
—
|
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: Das Lied von der Erde | Statement: [Hans Bethge, workUsedAsTextFor, Das Lied von der Erde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workUsedAsTextFor Context triple: [Hans Bethge, workUsedAsTextFor, Das Lied von der Erde]
-
A.
workUsedFor
Indicates that a particular work (such as a document, artwork, or dataset) is employed or utilized for a specific purpose, task, or function.
-
B.
workUsedAs
chosen
Indicates that one work is employed or utilized in the creation, performance, or presentation of another work.
-
C.
usedInWritingFor
Indicates that something (e.g., a tool, material, or medium) is employed as part of the process or context of writing for a particular purpose or audience.
-
D.
usedInWriting
Indicates that something (such as a tool, material, or medium) is employed as part of the process or act of writing.
-
E.
notableWorkUsed
Indicates that a particular notable work is utilized, referenced, or incorporated in relation to another entity or context.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:12 a.m.