Triple

T17472973
Position Surface form Disambiguated ID Type / Status
Subject Brutus XXII E425464 entity
Predicate critiquesAspectOf P82153 FINISHED
Object scope of federal legislative power 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: scope of federal legislative power | Statement: [Brutus XXII, critiquesAspectOf, scope of federal legislative power]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: critiquesAspectOf
Context triple: [Brutus XXII, critiquesAspectOf, scope of federal legislative power]
  • A. critiquesAspect chosen
    Indicates that one entity evaluates and expresses critical judgment about a particular aspect or component of another entity.
  • B. critiquesConcept
    Indicates that one entity analyzes, evaluates, or challenges the ideas or principles represented by another entity.
  • C. evaluationAspect
    Indicates the specific dimension or criterion of performance or quality that is being assessed within an evaluation.
  • D. criticizedConstruct
    Indicates that one entity expressed disapproval or negative judgment about another entity’s constructed work, idea, or creation.
  • E. criticObjective
    Indicates that an entity serves as the target or focus of a critic’s evaluation, commentary, or judgment.
  • 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_69d889dbc2e88190b18ea6115e819258 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451b990848190b2e8510d67e94b79 completed April 19, 2026, 3:53 a.m.
PD Predicate disambiguation batch_69e3b4f341c88190adabe526d8903b05 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:47 a.m.