Triple

T896664
Position Surface form Disambiguated ID Type / Status
Subject Telemachus E19360 entity
Predicate spouseTraditionNote P20830 FINISHED
Object Different later traditions pair Telemachus with Circe or Nausicaa 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: Different later traditions pair Telemachus with Circe or Nausicaa | Statement: [Telemachus, spouseTraditionNote, Different later traditions pair Telemachus with Circe or Nausicaa]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: spouseTraditionNote
Context triple: [Telemachus, spouseTraditionNote, Different later traditions pair Telemachus with Circe or Nausicaa]
  • A. spouseFamily
    Indicates a family relationship formed through marriage, such as between a person and their spouse’s relatives.
  • B. spouse
    Indicates that two entities are married to each other in a legally or socially recognized partnership.
  • C. spouseNotableFor
    Indicates that a person's spouse is recognized or distinguished for a particular achievement, role, or characteristic.
  • D. spouseMemberOf
    Indicates that a person’s spouse is a member of a specified group, organization, or entity.
  • E. spouseOrder
    Indicates the position or sequence of a person among multiple spouses in a marital relationship.
  • 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_69a4939d37188190848be3d426ebc9ae completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ad2550c88190a624eb5627d472ad completed March 1, 2026, 9:18 p.m.
PD Predicate disambiguation batch_69a4aa94f7c881908deeb62308942e19 completed March 1, 2026, 9:07 p.m.
PDg Predicate description generation batch_69a4ab4a38ec8190915916d80299ab55 completed March 1, 2026, 9:10 p.m.
Created at: March 1, 2026, 7:39 p.m.