Triple

T10825900
Position Surface form Disambiguated ID Type / Status
Subject Benevolent Dictator For Life (historical) E255496 entity
Predicate roleTypicallyHeldBy P18942 FINISHED
Object original project creator 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: original project creator | Statement: [Benevolent Dictator For Life (historical), roleTypicallyHeldBy, original project creator]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleTypicallyHeldBy
Context triple: [Benevolent Dictator For Life (historical), roleTypicallyHeldBy, original project creator]
  • A. namedPersonRole
    Indicates that a person is identified by name as holding a specific role or position in a given context.
  • B. typeOfRole
    Indicates that one entity specifies the kind or category of role that another entity holds or performs.
  • C. officeHolderRoleFor
    Indicates that a specific role or position is held by an office holder within an organization or governing body.
  • D. typicalRole chosen
    Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
  • E. officeHolderRoleIn
    Indicates that an entity holds or has held a specific role or position within a particular office or organizational context.
  • 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_69d6aa8081448190a9324184f2bd1c26 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d734d1c24881909f56d56207cccbef completed April 9, 2026, 5:10 a.m.
PD Predicate disambiguation batch_69d70d1bf3648190b36fa96ea018e0dc completed April 9, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:19 p.m.