Triple
T29989316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crocifissione di sant'Andrea |
E761826
|
entity |
| Predicate | tipoDiOpera |
P168726
|
FINISHED |
| Object | pala d'altare |
—
|
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: pala d'altare | Statement: [Crocifissione di sant'Andrea, tipoDiOpera, pala d'altare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tipoDiOpera Context triple: [Crocifissione di sant'Andrea, tipoDiOpera, pala d'altare]
-
A.
theatricalGenre
Indicates the specific theatrical genre or style to which a performance, play, or production belongs.
-
B.
theatreType
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
C.
theatricalProductionType
Indicates the specific kind or category of a theatrical production (such as play, musical, opera, etc.) that characterizes the relationship.
-
D.
musicalTheatreType
Indicates the specific category or style of musical theatre to which a work, production, or performance belongs.
-
E.
musicalTheatreWorkType
Indicates the specific type or category of a musical theatre work that characterizes the nature of the production.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791985c08190815809bcc3258be8 |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 29, 2026, 6:37 p.m.