Triple

T28809039
Position Surface form Disambiguated ID Type / Status
Subject Theatine Church of St. Cajetan E727457 entity
Predicate architect P184 FINISHED
Object Antonio Viscardi
Antonio Viscardi was an architect known for his work on the Theatine Church of St. Cajetan in Munich, a prominent example of Baroque ecclesiastical architecture.
E2054660 NE 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: Antonio Viscardi | Statement: [Theatine Church of St. Cajetan, architect, Antonio Viscardi]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Antonio Viscardi
Triple: [Theatine Church of St. Cajetan, architect, Antonio Viscardi]
Generated description
Antonio Viscardi was an architect known for his work on the Theatine Church of St. Cajetan in Munich, a prominent example of Baroque ecclesiastical architecture.

Provenance (5 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_69f0319c38948190bca746ad60fd25ba completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69f658b06e4c8190acbaf420e859b72c completed May 2, 2026, 8:04 p.m.
NED1 Entity disambiguation (via context triple) batch_6a359583c21c819083b2c2d5ac15ad11 completed June 19, 2026, 7:16 p.m.
NEDg Description generation batch_6a35a07b378c81909c246bc347c47ee3 completed June 19, 2026, 8:03 p.m.
NED2 Entity disambiguation (via description) batch_6a35a103368881908241e8cc960d871d completed June 19, 2026, 8:05 p.m.
Created at: April 28, 2026, 6:30 a.m.