Triple

T37463
Position Surface form Disambiguated ID Type / Status
Subject Government of Massachusetts E741 entity
Predicate appliesLegalSystem P605 FINISHED
Object common law 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: common law | Statement: [Government of Massachusetts, appliesLegalSystem, common law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appliesLegalSystem
Context triple: [Government of Massachusetts, appliesLegalSystem, common law]
  • A. legalSystem chosen
    Indicates the formal framework of laws, rules, and institutions that governs how legal matters are defined, interpreted, and enforced within a society or jurisdiction.
  • B. legalBasis
    Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
  • C. hasJurisdictionOver
    Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
  • D. legalContext
    Indicates that the relationship or action occurs within, is shaped by, or is relevant to a specific legal framework, proceeding, or set of legal norms.
  • E. legalArea
    Indicates the specific field or branch of law that a legal matter, case, or document pertains to.
  • 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_69a247a8f6c08190bac804906d62ed5a completed Feb. 28, 2026, 1:40 a.m.
NER Named-entity recognition batch_69a24bb753f081909cd8b25cfb8e08af completed Feb. 28, 2026, 1:58 a.m.
PD Predicate disambiguation batch_69a24ab4a6908190b6f355415ffe7948 completed Feb. 28, 2026, 1:53 a.m.
Created at: Feb. 28, 2026, 1:46 a.m.