Triple

T12551030
Position Surface form Disambiguated ID Type / Status
Subject British authorities in Greece E300094 entity
Predicate usedPoliticalPressure P91973 FINISHED
Object yes 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: yes | Statement: [British authorities in Greece, usedPoliticalPressure, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedPoliticalPressure
Context triple: [British authorities in Greece, usedPoliticalPressure, yes]
  • A. politicalPressureFrom chosen
    Indicates that one entity is exerting political influence or coercion on another to shape decisions, actions, or policies.
  • B. politicalRepercussion
    Indicates that an action, event, or decision leads to consequences or fallout within a political context, such as shifts in power, public opinion, or policy.
  • C. politicalInfluenceIn
    Indicates that an entity exerts or holds political influence within a specified place, jurisdiction, or political context.
  • D. politicalControl
    Indicates that one entity holds governing authority, influence, or decision-making power over the political actions or structure of another entity.
  • E. usesPoliticalLabel
    Indicates that one entity applies or assigns a specific political label or classification to another 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_69d6ada707008190aaec1238117c9379 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d95f5507b481908d13cc317b7402f6 completed April 10, 2026, 8:36 p.m.
PD Predicate disambiguation batch_69d95410d0b0819097646edd1b837104 completed April 10, 2026, 7:48 p.m.
Created at: April 8, 2026, 9:58 p.m.