Triple
T30906120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinfonie in h-Moll |
E787304
|
entity |
| Predicate | workTitleRefersTo |
P144370
|
FINISHED |
| Object | Symphony No. 8 in B minor, D 759 |
—
|
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: Symphony No. 8 in B minor, D 759 | Statement: [Sinfonie in h-Moll, workTitleRefersTo, Symphony No. 8 in B minor, D 759]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workTitleRefersTo Context triple: [Sinfonie in h-Moll, workTitleRefersTo, Symphony No. 8 in B minor, D 759]
-
A.
workTitle
Indicates the formal title or name of a work (such as a book, artwork, or composition) associated with an entity.
-
B.
workTitleReferences
Indicates that one work’s title explicitly mentions, cites, or alludes to another work.
-
C.
workTitleType
Indicates the specific category or type of a work’s title (e.g., main title, alternative title, translated title) in relation to that work.
-
D.
workTitleRelation
chosen
Indicates a relationship where one entity is the title or name of a work (such as a book, film, or artwork) associated with another entity.
-
E.
workTitleContains
Indicates that the title of a work includes a specified substring or term.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 8:50 p.m.