Triple

T4012085
Position Surface form Disambiguated ID Type / Status
Subject Supreme Court of New Hampshire E90666 entity
Predicate opinionsAre P29605 FINISHED
Object binding precedent on lower New Hampshire courts 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: binding precedent on lower New Hampshire courts | Statement: [Supreme Court of New Hampshire, opinionsAre, binding precedent on lower New Hampshire courts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: opinionsAre
Context triple: [Supreme Court of New Hampshire, opinionsAre, binding precedent on lower New Hampshire courts]
  • A. opinionBy
    Indicates that a particular opinion, viewpoint, or judgment is expressed or held by a specific entity.
  • B. hasDifferentOpinionsOn
    Indicates that two or more entities hold differing views or judgments regarding a particular topic, issue, or subject.
  • C. givesOpinionOn
    Indicates that one entity expresses a view, judgment, or evaluation about another entity or subject.
  • D. publishedOpinionsAre chosen
    Indicates that certain opinions have been made publicly available or formally released in a published form.
  • E. notableOpinion
    Indicates that one entity holds a significant or widely recognized opinion or viewpoint about 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_69aed95e44088190aff7d90a151b1b20 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefaec08dc8190a341809059554f84 completed March 9, 2026, 4:53 p.m.
PD Predicate disambiguation batch_69aef8fa6fec81909b1190ecbba61410 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:34 p.m.