Triple

T9516757
Position Surface form Disambiguated ID Type / Status
Subject Ajax (Sophocles) E229544 entity
Predicate mainCharacter P1183 FINISHED
Object Tecmessa E457116 NE 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: Tecmessa | Statement: [Ajax (Sophocles), mainCharacter, Tecmessa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tecmessa
Context triple: [Ajax (Sophocles), mainCharacter, Tecmessa]
  • A. Tecmessa chosen
    Tecmessa is a captive Trojan woman and the devoted consort of Ajax in Greek mythology, prominently featured in Sophocles’ tragedy "Ajax."
  • B. Machaon
    Machaon is a figure from Greek mythology, renowned as a skilled healer and son of the legendary physician Asclepius.
  • C. Velitrae
    Velitrae is an ancient town in Latium, Italy, historically notable as the birthplace of the future Roman emperor Augustus (Gaius Octavius).
  • D. Halistra
    Halistra is a small crofting settlement on the Waternish peninsula of the Isle of Skye in Scotland.
  • E. Telesia
    Telesia was an important ancient town in the region of Samnium in south-central Italy, known for its strategic and military significance in pre-Roman and Roman times.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca84777560819084cddd999badc1aa completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd987eefec8190b0db1928776bf02b completed April 1, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69d13a4aeb008190ae5d54367efe2722 completed April 4, 2026, 4:20 p.m.
Created at: March 30, 2026, 7:58 p.m.