Triple

T26076515
Position Surface form Disambiguated ID Type / Status
Subject Athens (through the story of Theseus) E657699 entity
Predicate mythicConflict P63719 FINISHED
Object war with Amazons 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: war with Amazons | Statement: [Athens (through the story of Theseus), mythicConflict, war with Amazons]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mythicConflict
Context triple: [Athens (through the story of Theseus), mythicConflict, war with Amazons]
  • A. mainConflict
    Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
  • B. mythicInstitution
    Indicates a relationship where an institution is characterized as belonging to the realm of myth, legend, or sacred narrative rather than ordinary historical or contemporary reality.
  • C. epicBattle
    Indicates a large-scale, intense conflict or confrontation between opposing entities, often marked by extraordinary stakes or dramatic significance.
  • D. hasMythologicalOpponents chosen
    Indicates that one entity is opposed or challenged by another entity within a mythological or legendary context.
  • E. mythicReputation
    Indicates a reputation or renown of legendary, larger-than-life status associated with an 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_69ee5bbe539081909efc7f9dd7c1b53c completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f621fcea1481909b6f8b3af1ee6820 completed May 2, 2026, 4:10 p.m.
PD Predicate disambiguation batch_69f620debeb48190b7db395fb86cf8d9 completed May 2, 2026, 4:05 p.m.
Created at: April 26, 2026, 7:34 p.m.