Triple

T12270800
Position Surface form Disambiguated ID Type / Status
Subject partial-birth abortion E292463 entity
Predicate hasDebateAspect P91795 FINISHED
Object maternal health exceptions 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: maternal health exceptions | Statement: [partial-birth abortion, hasDebateAspect, maternal health exceptions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDebateAspect
Context triple: [partial-birth abortion, hasDebateAspect, maternal health exceptions]
  • A. hasDebate
    Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
  • B. hasDebateTerm chosen
    Indicates that an entity is associated with, or characterized by, a specific term used in a debate or argumentative context.
  • C. hasDebatedPerson
    Indicates that one person has engaged in a debate or formal argumentative discussion with another person.
  • D. canDebate
    Indicates that one entity has the ability or permission to engage in a debate or argumentative discussion with another entity.
  • E. debatedAs
    Indicates that one entity is discussed or argued over in terms of being equivalent to, or serving in the role of, another entity within a debate or comparative argument.
  • 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_69d6ab6856488190b5d31178d5015f8e completed April 8, 2026, 7:24 p.m.
NER Named-entity recognition batch_69d9380a5e78819086bd4dfe9a83d1f5 completed April 10, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69d91c4a66cc819083ce6fcaf5042af6 completed April 10, 2026, 3:50 p.m.
Created at: April 8, 2026, 9:52 p.m.