Triple
T23227558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quattro pezzi sacri |
E581053
|
entity |
| Predicate | showsStyle |
P25796
|
FINISHED |
| Object | mature style of Giuseppe Verdi |
—
|
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: mature style of Giuseppe Verdi | Statement: [Quattro pezzi sacri, showsStyle, mature style of Giuseppe Verdi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsStyle Context triple: [Quattro pezzi sacri, showsStyle, mature style of Giuseppe Verdi]
-
A.
showType
Indicates the category or format in which something is presented or displayed (e.g., type of show, presentation, or display mode).
-
B.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
C.
exhibitStyle
Indicates that an entity displays, demonstrates, or embodies a particular style or manner of expression.
-
D.
styleFor
Indicates a relationship where one entity defines, specifies, or is used as the style or styling configuration applied to another entity.
-
E.
featuresStyle
chosen
Indicates that one entity exhibits, incorporates, or is characterized by a particular style associated with another entity.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922f5b4081908145d66ea7534493 |
completed | April 29, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.