Triple

T34263016
Position Surface form Disambiguated ID Type / Status
Subject Macer E879085 entity
Predicate hasNotableBearer P458 FINISHED
Object Aulus Licinius Macer
Aulus Licinius Macer was a 1st-century BC Roman historian and annalist known for his works on early Roman history and for being cited by later authors such as Livy.
E2099175 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: Aulus Licinius Macer | Statement: [Macer, hasNotableBearer, Aulus Licinius Macer]
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: Aulus Licinius Macer
Triple: [Macer, hasNotableBearer, Aulus Licinius Macer]
Generated description
Aulus Licinius Macer was a 1st-century BC Roman historian and annalist known for his works on early Roman history and for being cited by later authors such as Livy.

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_69f349b421cc8190b4b4655e1d612548 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f712c3cbe88190bdae67ad1c2ce195 completed May 3, 2026, 9:17 a.m.
NED1 Entity disambiguation (via context triple) batch_6a37211a58508190851ccdc26f51e2d2 completed June 20, 2026, 11:24 p.m.
NEDg Description generation batch_6a372200430c8190a70e010e1c3cad77 completed June 20, 2026, 11:28 p.m.
NED2 Entity disambiguation (via description) batch_6a37230e5a448190a0915ebeada6edd2 completed June 20, 2026, 11:32 p.m.
Created at: May 1, 2026, 1:56 a.m.