Triple

T29361455
Position Surface form Disambiguated ID Type / Status
Subject Supreme Council of Nagorno-Karabakh E744600 entity
Predicate could P166678 FINISHED
Object pass votes of confidence or no confidence in government 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: pass votes of confidence or no confidence in government | Statement: [Supreme Council of Nagorno-Karabakh, could, pass votes of confidence or no confidence in government]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: could
Context triple: [Supreme Council of Nagorno-Karabakh, could, pass votes of confidence or no confidence in government]
  • A. couldPass
    Indicates that one entity had the ability or potential to move through, overcome, or be accepted by another entity or barrier.
  • B. couldConsider
    Indicates that one entity has the potential or option to take another entity into account when making a decision, judgment, or evaluation.
  • C. have
    Indicates that one entity possesses, owns, or contains another entity or attribute.
  • D. cannot
    Indicates that one entity lacks the ability, permission, or possibility to perform an action or participate in a specified relationship with another entity.
  • E. couldIssue
    Indicates that one entity has the authority or ability to issue something (such as a document, command, or resource) to another entity.
  • 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_69f0a79aee588190b490f19d93c6e52d completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f6698892e88190b076bb0cdf159d8b completed May 2, 2026, 9:15 p.m.
PD Predicate disambiguation batch_69f660f4f7a88190b93c60d76b86c912 completed May 2, 2026, 8:39 p.m.
PDg Predicate description generation batch_69f661b47d088190934f63884a203261 completed May 2, 2026, 8:42 p.m.
Created at: April 28, 2026, 2:18 p.m.