Triple
T5012353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salzburg Cathedral |
E112653
|
entity |
| Predicate | baptismalFontUsedFor |
P60833
|
FINISHED |
| Object | baptism of Wolfgang Amadeus Mozart |
—
|
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: baptism of Wolfgang Amadeus Mozart | Statement: [Salzburg Cathedral, baptismalFontUsedFor, baptism of Wolfgang Amadeus Mozart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baptismalFontUsedFor Context triple: [Salzburg Cathedral, baptismalFontUsedFor, baptism of Wolfgang Amadeus Mozart]
-
A.
baptismPlace
Indicates the place where an individual was baptized.
-
B.
baptismName
Indicates the name an individual receives or uses specifically in the context of a baptism ceremony.
-
C.
baptized
Indicates that one entity performed or underwent the religious rite of baptism in relation to another entity or context.
-
D.
christenedBy
Indicates that an entity received its name or was formally dedicated through a christening performed by another entity.
-
E.
BenedictusType
Indicates that an entity is classified as a Benedictus, i.e., belonging to or exhibiting the defining characteristics of the Benedictus type.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730f12a481908a27c15dc73987c6 |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:35 p.m.