Triple

T20011708
Position Surface form Disambiguated ID Type / Status
Subject King Claudius E494604 entity
Predicate alliesWith P435 FINISHED
Object Laertes NE NERFINISHED

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: Laertes | Statement: [King Claudius, alliesWith, Laertes]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Laertes
Context triple: [King Claudius, alliesWith, Laertes]
  • A. Laertes
    Laertes is a figure in Greek mythology best known as the aging king of Ithaca and the father of the hero Odysseus in Homer's Odyssey.
  • B. Laertes chosen
    Laertes is a character in William Shakespeare's tragedy "Hamlet," known as Polonius's son who seeks revenge against Prince Hamlet for his father's death.
  • C. Gunde Rosenkrantz
    Gunde Rosenkrantz was a notable member of the Danish noble Rosenkrantz family, recognized as a prominent aristocrat and landowner in Denmark.
  • D. Rosencrantz
    Rosencrantz is a minor courtier and former schoolmate of Prince Hamlet who, along with Guildenstern, is used by King Claudius to spy on Hamlet in Shakespeare’s tragedy "Hamlet."
  • E. Fortinbras
    Fortinbras is a Norwegian prince in Shakespeare's "Hamlet" who serves as a foil to Hamlet and ultimately claims the Danish throne.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da626b2d748190886981ea90c8b2ea completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6623773d88190826616a02d3c3e69 completed April 20, 2026, 5:28 p.m.
Created at: April 11, 2026, 3:34 p.m.