Triple

T37925646
Position Surface form Disambiguated ID Type / Status
Subject Perasso E946084 entity
Predicate hasVariantSpelling P457 FINISHED
Object Perasso (Italian surname)
Perasso is an Italian family name of Ligurian origin, historically associated with the Genoa area and borne by several notable figures in Italian history and culture.
E2249151 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: Perasso (Italian surname) | Statement: [Perasso, hasVariantSpelling, Perasso (Italian surname)]
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: Perasso (Italian surname)
Triple: [Perasso, hasVariantSpelling, Perasso (Italian surname)]
Generated description
Perasso is an Italian family name of Ligurian origin, historically associated with the Genoa area and borne by several notable figures in Italian history and culture.

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_69f76ef3b7248190892fb9706423be7c completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbbd7cdce88190a93fc859f2eb7804 completed May 6, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a410cd6f6908190aed2b84404c1ee58 completed June 28, 2026, noon
NEDg Description generation batch_6a4111fed184819091455f68873a5090 completed June 28, 2026, 12:22 p.m.
NED2 Entity disambiguation (via description) batch_6a4112fe06f4819081c7c2fc8ad30e6f completed June 28, 2026, 12:26 p.m.
Created at: May 3, 2026, 4:20 p.m.