Triple

T369873
Position Surface form Disambiguated ID Type / Status
Subject Federal Court of Canada E8243 entity
Predicate hearsCasesFrom P1032 FINISHED
Object federal boards 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: federal boards | Statement: [Federal Court of Canada, hearsCasesFrom, federal boards]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hearsCasesFrom
Context triple: [Federal Court of Canada, hearsCasesFrom, federal boards]
  • A. cannotHearCasesFrom
    Indicates that one entity lacks the authority or ability to hear, consider, or adjudicate cases originating from another entity.
  • B. hasJurisdictionOver
    Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
  • C. appealsFrom
    Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
  • D. hasOriginalJurisdictionOver chosen
    Indicates that a legal body or authority has the power to hear and decide a case first, before any appellate review by higher bodies.
  • E. jurisdictionCovered
    Indicates that a particular jurisdiction or legal authority is included within the scope or coverage of another entity, rule, or arrangement.
  • 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_69a2e7f2ec648190b42bc7db424f8109 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ebfdb0608190b1794a871d0d237a completed Feb. 28, 2026, 1:22 p.m.
PD Predicate disambiguation batch_69a2e960d880819084b3df4e5137a1e2 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.