Triple

T38076614
Position Surface form Disambiguated ID Type / Status
Subject Marriage (Scotland) Act 1939 E950728 entity
Predicate reformsPractice P88043 FINISHED
Object irregular marriage in Scots 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: irregular marriage in Scots law | Statement: [Marriage (Scotland) Act 1939, reformsPractice, irregular marriage in Scots law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reformsPractice
Context triple: [Marriage (Scotland) Act 1939, reformsPractice, irregular marriage in Scots law]
  • A. reformsBy
    Indicates that one entity initiates, implements, or is responsible for changes or improvements (reforms) affecting another entity.
  • B. reformsArea chosen
    Indicates that an entity is responsible for changing, improving, or restructuring a particular area or domain.
  • C. relatedReforms
    Indicates that one reform is connected or associated with another reform, typically through shared goals, content, or impact.
  • D. associatedReforms
    Indicates a relationship where certain reforms are linked or connected to a given entity, such as a policy, event, or individual.
  • E. reform
    Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
  • 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_69f76f02a6c48190a94f3c0b3ee90cf2 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fc4748843c8190931432653be4890c completed May 7, 2026, 8:03 a.m.
PD Predicate disambiguation batch_69fc45646ce481908caf292ff9f06e15 completed May 7, 2026, 7:55 a.m.
Created at: May 3, 2026, 4:21 p.m.