Triple

T38458738
Position Surface form Disambiguated ID Type / Status
Subject Publius Decius Mus (consul of 340 BCE) E912390 entity
Predicate hasSuccessorInOffice P33240 FINISHED
Object consuls of 339 BCE 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: consuls of 339 BCE | Statement: [Publius Decius Mus (consul of 340 BCE), hasSuccessorInOffice, consuls of 339 BCE]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSuccessorInOffice
Context triple: [Publius Decius Mus (consul of 340 BCE), hasSuccessorInOffice, consuls of 339 BCE]
  • A. hasCommitteeSuccessor
    Indicates that one committee is the successor or follow-up body to another committee, continuing its role or responsibilities.
  • B. successorOfficeHolder chosen
    Indicates that one office holder directly follows another in occupying the same official position.
  • C. successorOfficeTo
    Indicates that one office or position directly follows and replaces another in an official sequence or hierarchy.
  • D. successorOfficeEstablished
    Indicates that a new office or position was formally created to replace or succeed a previous one.
  • E. hasCorporateSuccessor
    Indicates that one corporate entity is the legal successor to another, inheriting its rights, obligations, or continuity of business.
  • 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_69f76e84e2dc81908badf05b3aafa9ea completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a0087de41c48190b2743a26b6d65409 completed May 10, 2026, 1:27 p.m.
PD Predicate disambiguation batch_6a00870a8bc48190be1385579b8cc1dd completed May 10, 2026, 1:24 p.m.
Created at: May 3, 2026, 4:31 p.m.