Triple

T36104002
Position Surface form Disambiguated ID Type / Status
Subject Filippo Terzi E1044298 entity
Predicate knownAs P39 FINISHED
Object Filippo Terzio
Filippo Terzio was a 16th-century Italian architect and military engineer active in the service of the Habsburg Monarchy, particularly known for his fortification works in Central Europe.
E2176220 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: Filippo Terzio | Statement: [Filippo Terzi, knownAs, Filippo Terzio]
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: Filippo Terzio
Triple: [Filippo Terzi, knownAs, Filippo Terzio]
Generated description
Filippo Terzio was a 16th-century Italian architect and military engineer active in the service of the Habsburg Monarchy, particularly known for his fortification works in Central Europe.

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_69f76e338e2c8190b7f3bc68bec76349 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b29329d4819095a75a385a02a57a completed May 3, 2026, 8:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a396df4ecec8190af64321f75f03e03 completed June 22, 2026, 5:16 p.m.
NEDg Description generation batch_6a396facb1bc8190a0651b7a41f719cd completed June 22, 2026, 5:23 p.m.
NED2 Entity disambiguation (via description) batch_6a3970784914819086898e230ba5f0f2 completed June 22, 2026, 5:27 p.m.
Created at: May 3, 2026, 4:08 p.m.