Triple

T33097369
Position Surface form Disambiguated ID Type / Status
Subject Sinalunga E846946 entity
Predicate hasReligiousBuilding P1191 FINISHED
Object Church of Santa Croce
The Church of Santa Croce is a historic Catholic church in the Tuscan town of Sinalunga, Italy, noted for its traditional architecture and local religious significance.
E2036954 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: Church of Santa Croce | Statement: [Sinalunga, hasReligiousBuilding, Church of Santa Croce]
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: Church of Santa Croce
Triple: [Sinalunga, hasReligiousBuilding, Church of Santa Croce]
Generated description
The Church of Santa Croce is a historic Catholic church in the Tuscan town of Sinalunga, Italy, noted for its traditional architecture and local religious significance.

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_69f3495590dc8190aa04f3dec74ce976 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d6a9d12881908087ba7b04049ec0 completed May 3, 2026, 5:01 a.m.
NED1 Entity disambiguation (via context triple) batch_6a34f02b316481909ba457919ef0d8c7 completed June 19, 2026, 7:30 a.m.
NEDg Description generation batch_6a350b3510408190b027b5cbbfec61fa completed June 19, 2026, 9:26 a.m.
NED2 Entity disambiguation (via description) batch_6a350fdc2f14819084a7d9eedf28c2a3 completed June 19, 2026, 9:46 a.m.
Created at: May 1, 2026, 1:26 a.m.