Triple

T10210885
Position Surface form Disambiguated ID Type / Status
Subject The Testament E242322 entity
Predicate hasLegalElement P9087 FINISHED
Object probate 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: probate law | Statement: [The Testament, hasLegalElement, probate law]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLegalElement
Context triple: [The Testament, hasLegalElement, probate law]
  • A. hasLegalInstrument chosen
    Indicates that there exists a formal legal document or instrument that establishes, governs, or records the relationship between the related entities.
  • B. hasLegalSubject
    Indicates that an entity serves as the legal subject (e.g., rights-holder or obligated party) in a legal relationship or context.
  • C. hasLegalRight
    Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
  • D. hasLegalFunction
    Indicates that an entity performs, fulfills, or is assigned a specific legal role, duty, or function within a legal or regulatory context.
  • E. hasLegalForceIn
    Indicates that something (such as a law, regulation, or agreement) is legally valid, binding, and enforceable within a specified jurisdiction or context.
  • 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_69d381ae26c48190985abd0e25ee5d04 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d3aa22071c819095febd18dd607978 completed April 6, 2026, 12:42 p.m.
PD Predicate disambiguation batch_69d39559e5ac8190b88eca75956b7e6a completed April 6, 2026, 11:13 a.m.
Created at: April 6, 2026, 11:01 a.m.