Triple

T6762806
Position Surface form Disambiguated ID Type / Status
Subject Federal government E154634 entity
Predicate mayHaveStructure P73339 FINISHED
Object parliamentary system 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: parliamentary system | Statement: [Federal government, mayHaveStructure, parliamentary system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mayHaveStructure
Context triple: [Federal government, mayHaveStructure, parliamentary system]
  • A. hasHumanStructure
    Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
  • B. containsStructureFrom
    Indicates that one entity includes or incorporates a structural component originating from another entity.
  • C. usedStructure
    Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
  • D. proposedStructure
    Indicates that one entity has suggested or put forward another entity as a potential structure or structural arrangement.
  • E. hasStructureAbove
    Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
  • 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_69c688109c1c8190added9a221292af0 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d327e37081909d576e6eff9eec97 completed March 27, 2026, 6:57 p.m.
PD Predicate disambiguation batch_69c6d09227108190b253b91967831a85 completed March 27, 2026, 6:46 p.m.
PDg Predicate description generation batch_69c6d3264b7481908816a4d19543fb7b completed March 27, 2026, 6:57 p.m.
Created at: March 27, 2026, 2:12 p.m.