Triple

T9054964
Position Surface form Disambiguated ID Type / Status
Subject Murder of Geta E216973 entity
Predicate hasFamilyRelationContext P86123 FINISHED
Object conflict between sons of Septimius Severus 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: conflict between sons of Septimius Severus | Statement: [Murder of Geta, hasFamilyRelationContext, conflict between sons of Septimius Severus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFamilyRelationContext
Context triple: [Murder of Geta, hasFamilyRelationContext, conflict between sons of Septimius Severus]
  • A. belongsToFamily
    Indicates that an entity is a member of, or is associated as part of, a specific family group.
  • B. hasFamilialTieTo
    Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
  • C. hasFamilyRole
    Indicates that one entity holds a specific familial role or position in relation to another entity.
  • D. hasFamilyRelationInWork
    Indicates that there exists a family relationship between two entities within the context of a specific work (e.g., book, film, or other creative work).
  • E. containsFamily
    Indicates that one entity includes or encompasses members of a particular family group within it.
  • F. None of above. chosen

Provenance (4 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_69ca83d4425481909a319dab847724ec completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc7a7488188190b3dd6bc2f2377503 completed April 1, 2026, 1:52 a.m.
PD Predicate disambiguation batch_69cc5ee6d83c819095d8ed0779aa8511 completed March 31, 2026, 11:55 p.m.
PDg Predicate description generation batch_69cc5f4f1cb48190a025d1b3d8d7a790 completed March 31, 2026, 11:57 p.m.
Created at: March 30, 2026, 7:10 p.m.