Triple

T33380653
Position Surface form Disambiguated ID Type / Status
Subject Gavorrano E854766 entity
Predicate hasTouristAttraction P530 FINISHED
Object Teatro delle Rocce
Teatro delle Rocce is an open-air theater built within a former mining quarry near Gavorrano in Tuscany, Italy, known for its striking natural setting and cultural events.
E2050125 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: Teatro delle Rocce | Statement: [Gavorrano, hasTouristAttraction, Teatro delle Rocce]
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: Teatro delle Rocce
Triple: [Gavorrano, hasTouristAttraction, Teatro delle Rocce]
Generated description
Teatro delle Rocce is an open-air theater built within a former mining quarry near Gavorrano in Tuscany, Italy, known for its striking natural setting and cultural events.

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_69f3496ca10c8190908640d18fa00832 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e00147d48190880fdcb31be37dcc completed May 3, 2026, 5:41 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3576e7fcd8819082808a70e85c780d completed June 19, 2026, 5:05 p.m.
NEDg Description generation batch_6a357ae74b608190bd96b8c1d87ffe0c completed June 19, 2026, 5:22 p.m.
NED2 Entity disambiguation (via description) batch_6a357b6f2a248190b4e8f475a320e159 completed June 19, 2026, 5:25 p.m.
Created at: May 1, 2026, 1:35 a.m.