Triple

T33377785
Position Surface form Disambiguated ID Type / Status
Subject Lucius Caecilius Metellus Dalmaticus E854681 entity
Predicate nomen gentilicium P141718 FINISHED
Object Caecilius NE NERFINISHED

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: Caecilius | Statement: [Lucius Caecilius Metellus Dalmaticus, nomen gentilicium, Caecilius]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nomen gentilicium
Context triple: [Lucius Caecilius Metellus Dalmaticus, nomen gentilicium, Caecilius]
  • A. gentilicium chosen
    Indicates that an entity’s family or clan affiliation is expressed through a gentilic (family) name.
  • B. praenomenOrNomen
    Indicates that the related name element functions either as a personal given name (praenomen) or as a family/clan name (nomen) within a naming system.
  • C. usesGentilicFor
    Indicates that one entity refers to another using a gentilic (a demonym or term denoting origin, nationality, or regional affiliation).
  • D. onomasticType
    Indicates the specific kind or category of a name (e.g., personal, place, or other name type) that characterizes the naming relationship.
  • E. adoptiveNomen
    Indicates a naming relationship where one entity has taken on or been given the name of another in an adoptive or non-biological sense.
  • 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_69f3496ca10c8190908640d18fa00832 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6dfff88848190833cb929eab3c818 completed May 3, 2026, 5:41 a.m.
PD Predicate disambiguation batch_69f6de0c821c8190ae3ebda9dfdd0064 completed May 3, 2026, 5:33 a.m.
Created at: May 1, 2026, 1:35 a.m.