Triple

T31010207
Position Surface form Disambiguated ID Type / Status
Subject Bibbiena E790188 entity
Predicate hasHeritageSite P923 FINISHED
Object Oratorio di San Francesco
The Oratorio di San Francesco is a historic religious oratory in the Tuscan town of Bibbiena, Italy, notable for its artistic and devotional significance.
E1946273 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: Oratorio di San Francesco | Statement: [Bibbiena, hasHeritageSite, Oratorio di San Francesco]
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: Oratorio di San Francesco
Triple: [Bibbiena, hasHeritageSite, Oratorio di San Francesco]
Generated description
The Oratorio di San Francesco is a historic religious oratory in the Tuscan town of Bibbiena, Italy, notable for its artistic and devotional 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_69f224c73ca48190a1e46cb58ad4045b completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69447db808190bd985ad96f09dd60 completed May 3, 2026, 12:18 a.m.
NED1 Entity disambiguation (via context triple) batch_6a29389bd3c481908f4fb8aa78a033ca completed June 10, 2026, 10:12 a.m.
NEDg Description generation batch_6a29399635288190a730fb5a0d03b20a completed June 10, 2026, 10:16 a.m.
NED2 Entity disambiguation (via description) batch_6a293aadb0248190929ceb43625c5b28 completed June 10, 2026, 10:21 a.m.
Created at: April 29, 2026, 8:57 p.m.