Triple

T36502245
Position Surface form Disambiguated ID Type / Status
Subject Italian communes of the Lombard League E899360 entity
Predicate hasMember P10 FINISHED
Object Alessandria
Alessandria is a historic city and comune in the Piedmont region of northern Italy, known for its strategic military past and role in medieval Italian politics.
E238351 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: Alessandria | Statement: [Italian communes of the Lombard League, hasMember, Alessandria]
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: Alessandria
Triple: [Italian communes of the Lombard League, hasMember, Alessandria]
Generated description
Alessandria is a historic city and comune in the Piedmont region of northern Italy, known for its strategic military past and role in medieval Italian politics.

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_69f76e5b92088190933afda3f7531dd4 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7c1c4a2188190a3d153bbbe837579 completed May 3, 2026, 9:44 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3a20b31b3081908d9e34ad87727732 completed June 23, 2026, 5:59 a.m.
NEDg Description generation batch_6a3a223909648190859223424fc876ef completed June 23, 2026, 6:05 a.m.
NED2 Entity disambiguation (via description) batch_6a3a22aa6b788190bed3fe999f1534ee completed June 23, 2026, 6:07 a.m.
Created at: May 3, 2026, 4:10 p.m.