Triple

T37870853
Position Surface form Disambiguated ID Type / Status
Subject Lake Pergusa E944600 entity
Predicate hasNearbyFacility P5648 FINISHED
Object Autodromo di Pergusa
Autodromo di Pergusa is a motor racing circuit in Sicily, Italy, known for encircling Lake Pergusa and hosting various national and international racing events.
E2246711 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: Autodromo di Pergusa | Statement: [Lake Pergusa, hasNearbyFacility, Autodromo di Pergusa]
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: Autodromo di Pergusa
Triple: [Lake Pergusa, hasNearbyFacility, Autodromo di Pergusa]
Generated description
Autodromo di Pergusa is a motor racing circuit in Sicily, Italy, known for encircling Lake Pergusa and hosting various national and international racing 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_69f76eef55d481908ca6660b4b532550 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbb281901c819089c3833a778791f8 completed May 6, 2026, 9:28 p.m.
NED1 Entity disambiguation (via context triple) batch_6a410426df208190a8c5f2a14f4e9935 completed June 28, 2026, 11:23 a.m.
NEDg Description generation batch_6a4104f806508190ac10d8c5d0e6d6ad completed June 28, 2026, 11:26 a.m.
NED2 Entity disambiguation (via description) batch_6a4105bc112c8190ac137601aba2ed1f completed June 28, 2026, 11:30 a.m.
Created at: May 3, 2026, 4:19 p.m.