Triple

T13050473
Position Surface form Disambiguated ID Type / Status
Subject Praetorian Prefect E327435 entity
Predicate hasNotableOfficeHolder P537 FINISHED
Object Timesitheus E399585 NE 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: Timesitheus | Statement: [Praetorian Prefect, hasNotableOfficeHolder, Timesitheus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Timesitheus
Context triple: [Praetorian Prefect, hasNotableOfficeHolder, Timesitheus]
  • A. Timesitheus chosen
    Timesitheus was a prominent 3rd-century Roman statesman and praetorian prefect who became a key advisor and father-in-law to Emperor Gordian III.
  • B. Timoteus
    Timoteus is a male given name, commonly used in various European languages and derived from the biblical name Timothy.
  • C. Thestius
    Thestius is a figure in Greek mythology, a king of Aetolia and notable ancestor within several heroic bloodlines.
  • D. Tryphon
    Tryphon was a Seleucid usurper and king in the 2nd century BCE who seized control of parts of the Syrian kingdom during the Maccabean period.
  • E. Catreus
    Catreus is a figure in Greek mythology, a son of King Minos of Crete whose tragic fate is tied to a prophecy that he would be killed by one of his own children.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8076e64308190904fb5c93517c901 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d980b98fa081908cfa92116799e874 completed April 10, 2026, 10:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6cbda9b548190a10a4835b2c75fdc completed May 3, 2026, 4:15 a.m.
Created at: April 9, 2026, 8:57 p.m.