Triple

T35741336
Position Surface form Disambiguated ID Type / Status
Subject CSCE human dimension institutions E1033041 entity
Predicate normativeArea P49097 FINISHED
Object civil and political rights 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: civil and political rights | Statement: [CSCE human dimension institutions, normativeArea, civil and political rights]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: normativeArea
Context triple: [CSCE human dimension institutions, normativeArea, civil and political rights]
  • A. regulatedArea
    Indicates that an area is subject to specific rules, controls, or restrictions imposed by an authority.
  • B. regulatesArea
    Indicates that one entity exercises control or governance over the spatial extent, scope, or domain of another entity.
  • C. assessmentAreaDefinedBy
    Indicates that the scope or domain of an assessment is specified or delimited by a particular area or boundary.
  • D. canonicalArea
    Indicates that an entity is associated with a standardized or primary geographic or spatial area that represents its main or official location.
  • E. areaOfAuthority chosen
    Indicates the domain, region, or scope within which an entity has official power, control, or responsibility.
  • 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_69f76e119d508190a3873cb302063832 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a34f8ee08190a040304635539a8f completed May 3, 2026, 7:34 p.m.
PD Predicate disambiguation batch_69f7a06f125c8190843af194f042a465 completed May 3, 2026, 7:22 p.m.
Created at: May 3, 2026, 4:06 p.m.