Triple
T31729132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWV 111 |
E809806
|
entity |
| Predicate | subjectWorkComposer |
P184869
|
FINISHED |
| Object | Richard Wagner |
—
|
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: Richard Wagner | Statement: [WWV 111, subjectWorkComposer, Richard Wagner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectWorkComposer Context triple: [WWV 111, subjectWorkComposer, Richard Wagner]
-
A.
subjectOfWork
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
-
B.
subjectComposer
chosen
Indicates that the subject is the composer or creator of a musical work or composition.
-
C.
subjectOfWorkBy
Indicates that one entity is the main topic or focus of a work (such as a book, article, or artwork) created by another entity.
-
D.
associatedWorkComposer
Indicates that a person or entity is the composer responsible for creating the associated work.
-
E.
basedOnWorkComposer
Indicates that one work is derived from, adapted from, or otherwise created on the basis of another work by the specified composer.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 30, 2026, 11:21 p.m.