Triple

T28772950
Position Surface form Disambiguated ID Type / Status
Subject gens Sergia E726459 entity
Predicate hasPraenomenUsed P106104 FINISHED
Object Gnaeus
Gnaeus is a common Roman praenomen (given name) historically used by members of the gens Sergia and other Roman families.
E222442 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: Gnaeus | Statement: [gens Sergia, hasPraenomenUsed, Gnaeus]
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: Gnaeus
Triple: [gens Sergia, hasPraenomenUsed, Gnaeus]
Generated description
Gnaeus is a common Roman praenomen (given name) historically used by members of the gens Sergia and other Roman families.

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_69f03199997c8190b6ae43fb19312443 completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69ff1b28eae881908891c92c36039864 completed May 9, 2026, 11:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a25f0e9dbc88190a47749415286bd4e completed June 7, 2026, 10:30 p.m.
NEDg Description generation batch_6a25fdafe45881909fbdd01d1eefa762 completed June 7, 2026, 11:24 p.m.
NED2 Entity disambiguation (via description) batch_6a26029f7f84819089f6a5d042ba9cfa completed June 7, 2026, 11:45 p.m.
Created at: April 28, 2026, 6:16 a.m.