Triple

T35686645
Position Surface form Disambiguated ID Type / Status
Subject Tusculan family of Rome E1031166 entity
Predicate hasMember P10 FINISHED
Object Ptolemy II of Tusculum
Ptolemy II of Tusculum was a medieval nobleman from the powerful Tusculan family that dominated Roman politics and the papacy in the 10th–11th centuries.
E2153367 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: Ptolemy II of Tusculum | Statement: [Tusculan family of Rome, hasMember, Ptolemy II of Tusculum]
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: Ptolemy II of Tusculum
Triple: [Tusculan family of Rome, hasMember, Ptolemy II of Tusculum]
Generated description
Ptolemy II of Tusculum was a medieval nobleman from the powerful Tusculan family that dominated Roman politics and the papacy in the 10th–11th centuries.

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_69f76e0bb6608190ad3a1880be54a17d completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a07937988190841ae789d824406d completed May 3, 2026, 7:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a387d087788819087f885cf1745f9fc completed June 22, 2026, 12:08 a.m.
NEDg Description generation batch_6a387e0b606c819093d074bde21518d2 completed June 22, 2026, 12:12 a.m.
NED2 Entity disambiguation (via description) batch_6a3880fb52d4819099c2bdba7e7d948f completed June 22, 2026, 12:25 a.m.
Created at: May 3, 2026, 4:05 p.m.