Triple

T14200844
Position Surface form Disambiguated ID Type / Status
Subject Legislative and Legal Affairs Committee E351959 entity
Predicate preDebateStage P113183 FINISHED
Object examines bills before plenary debate 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: examines bills before plenary debate | Statement: [Legislative and Legal Affairs Committee, preDebateStage, examines bills before plenary debate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: preDebateStage
Context triple: [Legislative and Legal Affairs Committee, preDebateStage, examines bills before plenary debate]
  • A. debateOrganizer
    Indicates that one entity is responsible for organizing, coordinating, or managing a debate involving another entity or entities.
  • B. debateModerator
    Indicates that one entity serves as the moderator overseeing and managing a debate involving another entity or entities.
  • C. mainDebater
    Indicates that an entity serves as the primary or lead participant in a debate or argumentative exchange.
  • D. hasDebate
    Indicates that there is a formal discussion or argument between entities, typically presenting opposing viewpoints on a topic.
  • E. canDebate
    Indicates that one entity has the ability or permission to engage in a debate or argumentative discussion with another entity.
  • F. None of above. chosen

Provenance (4 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_69d827894ac0819097803e57f3227b23 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61f472548190a1a7edc40526eac3 completed April 14, 2026, 3:49 p.m.
PD Predicate disambiguation batch_69de05bcd7d48190a4848d9320404aa6 completed April 14, 2026, 9:15 a.m.
PDg Predicate description generation batch_69de239a02e881909b0e2679487e4ab2 completed April 14, 2026, 11:23 a.m.
Created at: April 10, 2026, 1:04 a.m.