Triple

T3319609
Position Surface form Disambiguated ID Type / Status
Subject Amphictyon E69762 entity
Predicate spouse P13 FINISHED
Object Cranaë E27945 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: Cranaë | Statement: [Amphictyon, spouse, Cranaë]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cranaë
Context triple: [Amphictyon, spouse, Cranaë]
  • A. Hesperethusa
    Hesperethusa is a genus of flowering plants in the citrus family Rutaceae, known for species such as Hesperethusa crenulata (also called Limonia crenulata) that are native to South and Southeast Asia.
  • B. Osphranter
    Osphranter is a genus of large Australian marsupials that includes several species of kangaroos and wallaroos.
  • C. Hyas chosen
    Hyas is a figure in Greek mythology, often associated with the Hyades as their brother and linked to myths explaining the origin of certain constellations or rain-bringing stars.
  • D. Orlybus
    Orlybus is a dedicated airport shuttle bus service connecting central Paris with Orly Airport.
  • E. Maurus
    Maurus is a masculine given name of Latin origin, historically associated with early Christian saints and used as a variant of names like Maurice.
  • 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_69ad85a0bb048190a5458d2738012d61 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb13a4e948190841134d6ae6ef432 completed March 8, 2026, 5:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69b2f40055a48190afe401a488d3ae34 completed March 12, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:11 p.m.