Triple

T36565633
Position Surface form Disambiguated ID Type / Status
Subject Aemilii Regilli E901967 entity
Predicate hasFamilyCognomen P109315 FINISHED
Object Regillus 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: Regillus | Statement: [Aemilii Regilli, hasFamilyCognomen, Regillus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFamilyCognomen
Context triple: [Aemilii Regilli, hasFamilyCognomen, Regillus]
  • A. memberHasCognomen chosen
    Indicates that a member is associated with or bears a specific cognomen (surname or additional family name).
  • B. hasFamilyNameOf
    Indicates that one entity bears or uses the same family name (surname) as another entity.
  • C. hasAncestralFamilyName
    Indicates that an entity bears or is associated with a family name inherited from its ancestors.
  • D. hasBaseSurname
    Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
  • E. isPaternalFamilyNameOf
    Indicates that one name is the paternal (father’s-side) family surname borne by a given person.
  • 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_69f76e6416708190a9754b8c52d4e453 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fe72dca2f08190beff17de3d2aada6 completed May 8, 2026, 11:33 p.m.
PD Predicate disambiguation batch_69fe70bca8d08190b810e1e616ceac44 completed May 8, 2026, 11:24 p.m.
Created at: May 3, 2026, 4:11 p.m.