Triple

T38076448
Position Surface form Disambiguated ID Type / Status
Subject Marriage Act 1753 E950724 entity
Predicate notApplicableInJurisdiction P189938 FINISHED
Object Scotland NE NERFINISHED

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: Scotland | Statement: [Marriage Act 1753, notApplicableInJurisdiction, Scotland]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notApplicableInJurisdiction
Context triple: [Marriage Act 1753, notApplicableInJurisdiction, Scotland]
  • A. appliedInJurisdiction
    Indicates that a rule, decision, or action is put into effect or holds legal force within a specified jurisdiction.
  • B. existsInJurisdiction
    Indicates that an entity is located within, falls under, or is subject to the authority of a particular legal or administrative jurisdiction.
  • C. usesJurisdiction
    Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
  • D. hasNoJurisdictionOver
    Indicates that one entity lacks the legal authority or power to govern, regulate, or make binding decisions over another entity or matter.
  • E. usedForJurisdiction
    Indicates that something (such as a rule, document, or authority) is applied to define, govern, or determine the scope of a particular jurisdiction.
  • 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_69f76f02a6c48190a94f3c0b3ee90cf2 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fc44c7e73c819082d4fc1900fb9632 completed May 7, 2026, 7:52 a.m.
PD Predicate disambiguation batch_69fbc8efffbc8190a139798ad1880526 completed May 6, 2026, 11:04 p.m.
PDg Predicate description generation batch_69fc44c67118819088accfeded7b449e completed May 7, 2026, 7:52 a.m.
Created at: May 3, 2026, 4:21 p.m.