Triple

T22383169
Position Surface form Disambiguated ID Type / Status
Subject Plenary Chamber E553324 entity
Predicate hasFormerPrimaryUser P45212 FINISHED
Object Members of the German Bundestag 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: Members of the German Bundestag | Statement: [Plenary Chamber, hasFormerPrimaryUser, Members of the German Bundestag]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFormerPrimaryUser
Context triple: [Plenary Chamber, hasFormerPrimaryUser, Members of the German Bundestag]
  • A. hasFormerPrimaryTenant chosen
    Indicates that an entity previously served as the main or principal tenant of another entity, but no longer holds that status.
  • B. hasFormerIdentity
    Indicates that an entity previously had a different identity, name, or role before its current one.
  • C. hasSecondaryUser
    Indicates that an entity is associated with an additional, non-primary user who also has access to or control over it.
  • D. hasFormerParticipant
    Indicates that an entity once participated in an activity, event, or organization but is no longer a current participant.
  • E. hasFormerPatron
    Indicates that an entity previously served as a patron or sponsor of another entity, but no longer holds that role.
  • 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_69e11e4cf87c8190a1ff474daec326b7 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1582d8e548190a7330de49d519675 completed April 29, 2026, 1 a.m.
PD Predicate disambiguation batch_69e73015484c8190a9a0b9f554b61a81 completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 8:45 p.m.