Triple

T17260842
Position Surface form Disambiguated ID Type / Status
Subject Atropa E419004 entity
Predicate namedAfter P63 FINISHED
Object Atropos E157575 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: Atropos | Statement: [Atropa, namedAfter, Atropos]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Atropos
Context triple: [Atropa, namedAfter, Atropos]
  • A. Atropos chosen
    Atropos is the Fate in Greek mythology who determines the end of a mortal’s life by cutting their thread.
  • B. Moirae
    The Moirae are the three personified goddesses of fate in Greek mythology who determine the destinies and lifespans of gods and mortals alike.
  • C. Erinome
    Erinome is a small, irregular, retrograde moon of Jupiter belonging to the planet’s outer group of distant satellites.
  • D. Lachesis
    Lachesis is one of the three Moirai (Fates) in Greek mythology, responsible for measuring the length of each mortal’s life.
  • E. Sisygambis
    Sisygambis was a Persian noblewoman, mother of King Darius III of the Achaemenid Empire, known for her dignified conduct after being captured by Alexander the Great.
  • 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_69d886d9ab108190b70edd8d17aa1204 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42e70b00c8190b0380be08afae18d completed April 19, 2026, 1:22 a.m.
NED1 Entity disambiguation (via context triple) batch_6a017101d5dc8190ac6507344897b0f3 completed May 11, 2026, 6:02 a.m.
Created at: April 10, 2026, 5:39 a.m.