Triple

T35639414
Position Surface form Disambiguated ID Type / Status
Subject Invasion of Attica in 431 BC E1029815 entity
Predicate AthenianStrategy P108103 FINISHED
Object refusal to give open battle 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: refusal to give open battle | Statement: [Invasion of Attica in 431 BC, AthenianStrategy, refusal to give open battle]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: AthenianStrategy
Context triple: [Invasion of Attica in 431 BC, AthenianStrategy, refusal to give open battle]
  • A. AthenianCommander
    Indicates that the subject serves as a military commander for the Athenians or the Athenian state.
  • B. GreekStrategy chosen
    Indicates a strategic approach or plan that is based on or characteristic of Greek methods, tactics, or principles.
  • C. AthenaBribe
    Indicates that one entity offers or gives something of value to another as a bribe, specifically involving or attributed to Athena.
  • D. functionInAthenianIdeology
    Indicates the role or purpose that something serves within the beliefs, values, and political worldview of Athenian society.
  • E. AthenianCommanderEscaped
    Indicates that an Athenian commander successfully fled or avoided capture in a given situation or event.
  • 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_69f76e087bdc8190a4794bf9c0bd7634 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79f4ab48c8190988340c0ee825ffa completed May 3, 2026, 7:17 p.m.
PD Predicate disambiguation batch_69f79e4d885881908a3612e2e75cf84f completed May 3, 2026, 7:13 p.m.
Created at: May 3, 2026, 4:05 p.m.