Triple

T2245045
Position Surface form Disambiguated ID Type / Status
Subject Federalist No. 78 E49482 entity
Predicate characterizesJudiciaryAs P36443 FINISHED
Object least dangerous branch 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: least dangerous branch | Statement: [Federalist No. 78, characterizesJudiciaryAs, least dangerous branch]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: characterizesJudiciaryAs
Context triple: [Federalist No. 78, characterizesJudiciaryAs, least dangerous branch]
  • A. judicialRole
    Indicates that one entity holds or performs a specific official function or position within the judicial system in relation to another entity or legal matter.
  • B. hasJudiciary
    Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
  • C. judicialBody
    Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
  • D. courtRole
    Indicates the specific capacity or position an entity holds within a court proceeding or judicial context.
  • E. roleInJudges
    Indicates that an entity holds or held a specific role, position, or function within a judicial body or among a group of judges.
  • F. None of above. chosen

Provenance (4 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.
PDg Predicate description generation batch_69abbe4252688190944491a450383450 completed March 7, 2026, 5:57 a.m.
Created at: March 4, 2026, 7:47 p.m.