Triple

T25557623
Position Surface form Disambiguated ID Type / Status
Subject 帝国議会 E640615 entity
Predicate 立法手続き上の役割 P4024 FINISHED
Object 法律案の審議・議決 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: 法律案の審議・議決 | Statement: [帝国議会, 立法手続き上の役割, 法律案の審議・議決]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: 立法手続き上の役割
Context triple: [帝国議会, 立法手続き上の役割, 法律案の審議・議決]
  • A. usesLegislativeProcess
    Indicates that an entity carries out its actions or decisions through a formal legislative procedure, such as proposing, debating, and enacting laws or regulations.
  • B. hasLegislativeProcess
    Indicates that there exists a specific legislative procedure or set of steps governing how laws or regulations are proposed, debated, and enacted for the related entity.
  • C. legislativeRole chosen
    Indicates that an entity holds or performs a specific official position, function, or duty within a legislative body or lawmaking process.
  • D. legislativeMechanism
    Indicates a relationship where a law, policy, or rule is created, modified, or enacted through a specific formal legislative process or procedure.
  • E. legislativeActOf
    Indicates a relationship where a legislative act is authored, enacted, or formally issued by a specific legislative body or authority.
  • 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_69e75dc1beb08190bac7d76b8d6e7bc4 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f8cb186c819099b247e4a8cbd367 completed May 2, 2026, 1:14 p.m.
PD Predicate disambiguation batch_69f468421ba08190880eac99135e5970 completed May 1, 2026, 8:45 a.m.
Created at: April 21, 2026, 3:44 p.m.