Triple

T12544993
Position Surface form Disambiguated ID Type / Status
Subject Clinton impeachment E299937 entity
Predicate significantLegalIssue P83607 FINISHED
Object definition of perjury 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: definition of perjury | Statement: [Clinton impeachment, significantLegalIssue, definition of perjury]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: significantLegalIssue
Context triple: [Clinton impeachment, significantLegalIssue, definition of perjury]
  • A. hasLegalIssue
    Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
  • B. significantLawSection
    Indicates that a particular section of law is especially relevant or important in the context of the described legal situation or relationship.
  • C. significantDispute
    Indicates a serious, often prolonged disagreement or conflict exists between the involved entities.
  • D. legalMatters
    Indicates that one entity is involved with, concerned about, or responsible for legal issues, processes, or obligations related to another entity or context.
  • E. legalDisputeSubject chosen
    Indicates that a legal dispute concerns, involves, or is specifically about the referenced subject or matter.
  • 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95f5507b481908d13cc317b7402f6 completed April 10, 2026, 8:36 p.m.
PD Predicate disambiguation batch_69d95410d0b0819097646edd1b837104 completed April 10, 2026, 7:48 p.m.
Created at: April 8, 2026, 9:57 p.m.