Triple

T10269096
Position Surface form Disambiguated ID Type / Status
Subject Vannius E240787 entity
Predicate characterizationByTacitus P49575 FINISHED
Object initially just and popular LITERAL 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: initially just and popular | Statement: [Vannius, characterizationByTacitus, initially just and popular]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: characterizationByTacitus
Context triple: [Vannius, characterizationByTacitus, initially just and popular]
  • A. characterizationByHistorians chosen
    Indicates how historians have described, interpreted, or evaluated a person, event, or phenomenon in their scholarly work.
  • B. RomanRepresentative
    Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
  • C. romanNomen
    Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
  • D. Chronica_subject
    Indicates that an entity serves as the subject or main focus of a chronicle, record, or historical account.
  • E. roleInRome
    Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
  • F. None of above.

Provenance (3 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_69d381a94c1881908fc38fc263d9b9c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d2872830819080fdfa816167d04c completed April 7, 2026, 9:46 a.m.
PD Predicate disambiguation batch_69d4d1ef6e6c81908a8ee52e4d28127b completed April 7, 2026, 9:44 a.m.
Created at: April 6, 2026, 11:35 a.m.