Triple
T15789096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica di Sant’Andrea della Valle |
E382814
|
entity |
| Predicate | apseFrescoSubject |
P107052
|
FINISHED |
| Object | Glory of Paradise |
—
|
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: Glory of Paradise | Statement: [Basilica di Sant’Andrea della Valle, apseFrescoSubject, Glory of Paradise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apseFrescoSubject Context triple: [Basilica di Sant’Andrea della Valle, apseFrescoSubject, Glory of Paradise]
-
A.
associatedWithSubject
chosen
Indicates a general relationship or connection between an entity and a subject, without specifying the exact nature of that association.
-
B.
annexASubject
Indicates that one entity formally incorporates another entity as a subordinate or dependent part under its control.
-
C.
subjectMVP
Indicates that the subject is considered the most valuable player (MVP) in a given context or event.
-
D.
annexBSubject
Indicates that one entity is the subject or main focus of Annex B in relation to another entity.
-
E.
adaptationSubject
Indicates that one entity serves as the source or subject matter that is adapted into another work or form.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e054048ff48190ad107c890ef73166 |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.