Triple
T29989302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crocifissione di sant'Andrea |
E761826
|
entity |
| Predicate | ambientazione |
P20834
|
FINISHED |
| Object | scena di martirio cristiano |
—
|
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: scena di martirio cristiano | Statement: [Crocifissione di sant'Andrea, ambientazione, scena di martirio cristiano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ambientazione Context triple: [Crocifissione di sant'Andrea, ambientazione, scena di martirio cristiano]
-
A.
ambientSpace
Indicates the surrounding or containing space within which an object, structure, or geometric entity is situated or defined.
-
B.
placeOfSetting
chosen
Indicates the location or environment where an event, scene, or situation takes place.
-
C.
tourEnvironment
Indicates that an entity conducts or participates in a tour within a particular environment or setting.
-
D.
luogo
Indicates that something is located, occurs, or exists in a particular place or location.
-
E.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
- 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_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_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:37 p.m.