Triple

T15095323
Position Surface form Disambiguated ID Type / Status
Subject Theban Triad E360522 entity
Predicate hasMember P10 FINISHED
Object Mut E201450 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: Mut | Statement: [Theban Triad, hasMember, Mut]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mut
Context triple: [Theban Triad, hasMember, Mut]
  • A. Mut chosen
    Mut is an ancient Egyptian mother goddess associated with kingship and protection, prominently worshipped at Thebes as a principal consort of Amun.
  • B. Mut
    Mut is a town in Egypt’s Western Desert that serves as the main administrative and population center of the Dakhla Oasis.
  • C. Mut
    Mut is a district and town in Turkey’s Mersin Province, known for its agricultural production—especially apricots—and its historical sites dating back to ancient times.
  • D. Mir
    Mir was a Soviet and later Russian modular space station that served as a long-term research outpost in low Earth orbit from 1986 to 2001.
  • E. Mir
    Mir is a historic town in present-day Belarus, known for its multicultural heritage and the UNESCO-listed Mir Castle Complex.
  • 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_69d85a035aa88190b52a139d3a1b7b6d completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0054571a48190a57055c0d6e90f82 completed April 15, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69feae21134c81908939ad6ce46703d8 completed May 9, 2026, 3:46 a.m.
Created at: April 10, 2026, 3:04 a.m.