Triple

T1126697
Position Surface form Disambiguated ID Type / Status
Subject Parliament of Singapore E24735 entity
Predicate hasLegislativeStructure P11711 FINISHED
Object unicameral 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: unicameral | Statement: [Parliament of Singapore, hasLegislativeStructure, unicameral]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLegislativeStructure
Context triple: [Parliament of Singapore, hasLegislativeStructure, unicameral]
  • A. legislatureStructure chosen
    Indicates how a legislative body is organized, such as its internal composition, chambers, and structural arrangement.
  • B. hasLegislatureType
    Indicates the specific form or system of legislature that an entity possesses or operates under.
  • C. hasLegislativePower
    Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
  • D. hasBicameralStructure
    Indicates that an entity possesses a two-chamber (two-house) internal organizational or legislative structure.
  • E. 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.
  • 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_69a4940712c88190aa244f3fc6070a65 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bc4bc21881909dcfe628f59f3e8c completed March 1, 2026, 10:23 p.m.
PD Predicate disambiguation batch_69a4bb4749ac8190b0fbddac2e9b2586 completed March 1, 2026, 10:18 p.m.
Created at: March 1, 2026, 7:44 p.m.