Triple

T31447964
Position Surface form Disambiguated ID Type / Status
Subject praefectus vigilum E802239 entity
Predicate hadAuthorityTo P142632 FINISHED
Object impose fines 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: impose fines | Statement: [praefectus vigilum, hadAuthorityTo, impose fines]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadAuthorityTo
Context triple: [praefectus vigilum, hadAuthorityTo, impose fines]
  • A. hasLegalAuthorityFrom
    Indicates that one entity possesses formal legal power, rights, or authorization that originates from or is granted by another entity.
  • B. usesAuthorityOf
    Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
  • C. hasLimitedAuthorityOver
    Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
  • D. hadOccupationAuthority
    Indicates that an entity held an official position or role that granted them recognized authority or power within an occupation or professional context.
  • E. hasPublicAuthority chosen
    Indicates that an entity possesses official power or legal authority to act on behalf of the public or a governing body.
  • 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_69f348c5a6bc819092a557e95438976f completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6a5f71b2c8190aade8a83f465be0c completed May 3, 2026, 1:33 a.m.
PD Predicate disambiguation batch_69f69fe66df08190958558d63ee623d9 completed May 3, 2026, 1:07 a.m.
Created at: April 30, 2026, 9:10 p.m.