Triple
T29180545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liebesträume |
E739733
|
entity |
| Predicate | sectionalFormOfNo3 |
P3120
|
FINISHED |
| Object | song-like with contrasting middle section |
—
|
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: song-like with contrasting middle section | Statement: [Liebesträume, sectionalFormOfNo3, song-like with contrasting middle section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionalFormOfNo3 Context triple: [Liebesträume, sectionalFormOfNo3, song-like with contrasting middle section]
-
A.
notableForm
Indicates that one entity is a significant or characteristic form, version, or manifestation of another entity.
-
B.
technicalForm
Indicates the specific technical format, method, or medium through which something is created, presented, or executed.
-
C.
filingForm
Indicates that an entity submits or completes a specific form or document, typically as part of an official or administrative process.
-
D.
regulatoryForm
Indicates the specific legal or organizational regulatory structure under which an entity is established or operates.
-
E.
section
chosen
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663444268819088b7976a7295d57a |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:57 a.m.