Triple

T30733703
Position Surface form Disambiguated ID Type / Status
Subject Egnatia gens E782487 entity
Predicate hasMember P10 FINISHED
Object Egnatius Rufus
Egnatius Rufus was a member of the plebeian Roman Egnatia gens, known from the late Roman Republic and early Empire.
E1929134 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: Egnatius Rufus | Statement: [Egnatia gens, hasMember, Egnatius Rufus]
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: Egnatius Rufus
Triple: [Egnatia gens, hasMember, Egnatius Rufus]
Generated description
Egnatius Rufus was a member of the plebeian Roman Egnatia gens, known from the late Roman Republic and early Empire.

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_69f224ad9f9c81908e02a79ae0001137 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f68ee54d1c8190a4c020394f7fb19a completed May 2, 2026, 11:55 p.m.
NED1 Entity disambiguation (via context triple) batch_6a289913cec48190963e940be54121e1 completed June 9, 2026, 10:52 p.m.
NEDg Description generation batch_6a289af04cc08190a45004a2c7d2e6b7 completed June 9, 2026, 11 p.m.
NED2 Entity disambiguation (via description) batch_6a289ba3fe2881909d2b7db74cf7aa82 completed June 9, 2026, 11:03 p.m.
Created at: April 29, 2026, 8:37 p.m.