Triple

T2245046
Position Surface form Disambiguated ID Type / Status
Subject Federalist No. 78 E49482 entity
Predicate claimsJudiciaryLacks P33370 FINISHED
Object control over the sword 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: control over the sword | Statement: [Federalist No. 78, claimsJudiciaryLacks, control over the sword]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: claimsJudiciaryLacks
Context triple: [Federalist No. 78, claimsJudiciaryLacks, control over the sword]
  • A. hasJudiciary
    Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
  • B. affectedCourt
    Indicates that a particular court is impacted or influenced by a specified action, decision, or legal matter.
  • C. jurisdictionDenied chosen
    Indicates that an authority or body has refused or lacks the legal power to hear, decide, or exercise control over a particular case, matter, or entity.
  • D. cannotHearCasesFrom
    Indicates that one entity lacks the authority or ability to hear, consider, or adjudicate cases originating from another entity.
  • E. hasJurisdictionOver
    Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
  • 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_69a88aa979788190ad6500f1d8eee2fc completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc0e8d5648190915ff689c7ca42bc completed March 7, 2026, 6:08 a.m.
PD Predicate disambiguation batch_69abbdb160248190aa75b38f11ad8602 completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:47 p.m.