Triple
T28332512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stabat Mater |
E717571
|
entity |
| Predicate | placeInRossiniOutput |
P177535
|
FINISHED |
| Object | major late sacred work |
—
|
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: major late sacred work | Statement: [Stabat Mater, placeInRossiniOutput, major late sacred work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInRossiniOutput Context triple: [Stabat Mater, placeInRossiniOutput, major late sacred work]
-
A.
placeInBrahmsOutput
Indicates that one entity occupies a specific position or location within the output or work produced by Brahms.
-
B.
placeInOpera
Indicates that one entity is a location or setting where an opera takes place or is staged.
-
C.
positionAmongLeonoreOvertures
Indicates the specific ordering or rank that an item holds within the set of Leonore overtures.
-
D.
eraWithinBeethovenOutput
Indicates that a given time period falls within the historical era corresponding to Beethoven’s active creative output.
-
E.
placeInBachCatalog
Indicates the position or entry number that a musical work occupies within the Bach catalog.
- F. None of above. chosen
Provenance (4 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 28, 2026, 12:33 a.m.