Triple
T37922761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor |
E946007
|
entity |
| Predicate | refersToWorkNumberInComposerOutput |
P32662
|
FINISHED |
| Object | fifth piano concerto |
—
|
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: fifth piano concerto | Statement: [Emperor, refersToWorkNumberInComposerOutput, fifth piano concerto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToWorkNumberInComposerOutput Context triple: [Emperor, refersToWorkNumberInComposerOutput, fifth piano concerto]
-
A.
workNumberInComposerOutput
chosen
Indicates that a specific work number appears in the output or catalog produced by a particular composer.
-
B.
workNumberInComposerLateOutput
Indicates that a specific work number appears in the later-period output of a particular composer.
-
C.
workNumberInMozartOutput
Indicates the ordinal work number assigned to a composition within the catalog of Mozart’s works.
-
D.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
E.
workNumberInOpus8
Indicates that a work is assigned a specific number within Opus 8 of a composer’s catalog.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
Created at: May 3, 2026, 4:20 p.m.