Triple

T24965482
Position Surface form Disambiguated ID Type / Status
Subject Sulmona E624729 entity
Predicate hasLandmark P105 FINISHED
Object Church of San Francesco della Scarpa
The Church of San Francesco della Scarpa is a historic Franciscan church in Sulmona, Italy, noted for its medieval origins and architectural significance.
E1670423 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 San Francesco della Scarpa | Statement: [Sulmona, hasLandmark, Church of San Francesco della Scarpa]
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 San Francesco della Scarpa
Triple: [Sulmona, hasLandmark, Church of San Francesco della Scarpa]
Generated description
The Church of San Francesco della Scarpa is a historic Franciscan church in Sulmona, Italy, noted for its medieval origins and architectural 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_69e2ff24512481908e9a72315b8d0354 completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f444d7f9e4819098276f05604b2f2a completed May 1, 2026, 6:14 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1067abe074819080ff876dc50eb745 completed May 22, 2026, 2:26 p.m.
NEDg Description generation batch_6a106907472881908bb4565bb581dbbd completed May 22, 2026, 2:32 p.m.
NED2 Entity disambiguation (via description) batch_6a10697c10bc8190a984f68d0bce5078 completed May 22, 2026, 2:34 p.m.
Created at: April 18, 2026, 6 a.m.