Triple

T1349243
Position Surface form Disambiguated ID Type / Status
Subject Tanco v. Haslam E28842 entity
Predicate plaintiffStatus P127 FINISHED
Object same-sex couples legally married in other jurisdictions 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: same-sex couples legally married in other jurisdictions | Statement: [Tanco v. Haslam, plaintiffStatus, same-sex couples legally married in other jurisdictions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: plaintiffStatus
Context triple: [Tanco v. Haslam, plaintiffStatus, same-sex couples legally married in other jurisdictions]
  • A. allegedStatus
    Indicates that a particular status or condition is claimed or asserted about an entity, but has not been confirmed as true.
  • B. appealStatus
    Indicates the current state or outcome of an appeal within a review or decision process.
  • C. status chosen
    Indicates the current condition, state, or standing of an entity within a given context.
  • D. statusDisputedBy
    Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
  • E. legalOutcome
    Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
  • 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_69a498571d248190a0ac9eb02d97097f completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c268745481908be649526c18e558 completed March 1, 2026, 10:49 p.m.
PD Predicate disambiguation batch_69a4bef5857c81909ae984feb85a26ca completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:56 p.m.