Triple
T10126576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Walküre |
E226229
|
entity |
| Predicate | leitmotifUsage |
P41002
|
FINISHED |
| Object | extensive |
—
|
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: extensive | Statement: [Die Walküre, leitmotifUsage, extensive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leitmotifUsage Context triple: [Die Walküre, leitmotifUsage, extensive]
-
A.
usesMotifsFrom
Indicates that one entity incorporates or draws upon recurring themes, patterns, or elements that originate from another entity.
-
B.
narrativeMotif
Indicates a recurring thematic element, pattern, or situation that appears across one or more narratives and helps structure or convey their underlying meanings.
-
C.
scriptUsedForMotto
Indicates that a particular writing system or script is used to render or express a given motto.
-
D.
featuresMotif
chosen
Indicates that something contains, incorporates, or prominently includes a particular recurring motif or pattern.
-
E.
lyricalMotive
Indicates a recurring musical or textual idea that serves as a unifying expressive element within a lyrical or vocal work.
- 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_69ca843057b48190a86730167f5d6b98 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2eef7388190b95ffd02814f2d1f |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.