Triple

T32541453
Position Surface form Disambiguated ID Type / Status
Subject cult of Jupiter Latiaris E831722 entity
Predicate requiredRiteFor P90349 FINISHED
Object assumption of consular office 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: assumption of consular office | Statement: [cult of Jupiter Latiaris, requiredRiteFor, assumption of consular office]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiredRiteFor
Context triple: [cult of Jupiter Latiaris, requiredRiteFor, assumption of consular office]
  • A. requiredTo chosen
    Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
  • B. requiredBy
    Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
  • C. earnRequirementType
    Indicates the type or category of requirement that must be fulfilled in order to earn or obtain something.
  • D. requiredOn
    Indicates that one entity must exist, be present, or be fulfilled on a specific other entity, date, or condition as a mandatory requirement.
  • E. requiredToProvide
    Indicates that one entity has an obligation or duty to supply or furnish something to another entity.
  • 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_69f34925fd08819084cfe4ec566cb704 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69ff0d80c0dc81909fbd12285c7a45c0 completed May 9, 2026, 10:33 a.m.
PD Predicate disambiguation batch_69ff0cd03e78819094895058f925fbfa completed May 9, 2026, 10:30 a.m.
Created at: May 1, 2026, 1:02 a.m.