Triple
T29989319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crocifissione di sant'Andrea |
E761826
|
entity |
| Predicate | autoreLuogoDiOrigine |
P55015
|
FINISHED |
| Object | Milano |
—
|
NE NERFINISHED |
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: Milano | Statement: [Crocifissione di sant'Andrea, autoreLuogoDiOrigine, Milano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: autoreLuogoDiOrigine Context triple: [Crocifissione di sant'Andrea, autoreLuogoDiOrigine, Milano]
-
A.
authorNationality
Indicates the relationship between an author and the country or nationality with which that author is identified.
-
B.
creatorPlaceOfBirth
Indicates that the place specified is the location where the creator of an entity was born.
-
C.
capitalOfOrigin
Indicates that one entity is the capital city associated with the origin (such as birthplace, founding place, or source location) of another entity.
-
D.
authorOrigin
chosen
Indicates that an author has a specific place, region, or country as their origin or background.
-
E.
countryOfNotableWork
Indicates the country with which a notable work is primarily associated, such as where it was created, set, or gained its significance.
- 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_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:37 p.m.