Triple

T14001320
Position Surface form Disambiguated ID Type / Status
Subject Battle of Grammos E336830 entity
Predicate belligerentIdeology P112105 FINISHED
Object anti-communism 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: anti-communism | Statement: [Battle of Grammos, belligerentIdeology, anti-communism]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: belligerentIdeology
Context triple: [Battle of Grammos, belligerentIdeology, anti-communism]
  • A. belligerentAgainst
    Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
  • B. belligerentInterest
    Indicates that an entity has a hostile, aggressive, or conflict-seeking attitude or stake toward another entity or situation.
  • C. conflictBelligerent
    Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
  • D. ideologyOfInsurgents
    Indicates the guiding beliefs, values, or political doctrine held by insurgent groups that shape their goals and actions.
  • E. coBelligerent
    Indicates that two or more parties are engaged in hostilities against a common enemy, typically as allies or coordinated participants in the same conflict.
  • 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_69d81c645c5c8190b1fd16a285a1b78a completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2ed06a50819093ddc64f55050689 completed April 14, 2026, 12:10 p.m.
PD Predicate disambiguation batch_69dd465dfbc4819090d8c61fd572d35f completed April 13, 2026, 7:39 p.m.
PDg Predicate description generation batch_69de01ed2098819088ec45069f6f2609 completed April 14, 2026, 8:59 a.m.
Created at: April 9, 2026, 10:19 p.m.