Triple

T17615485
Position Surface form Disambiguated ID Type / Status
Subject Thutmose I E429071 entity
Predicate tomb P196 FINISHED
Object KV20 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: KV20 | Statement: [Thutmose I, tomb, KV20]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KV20
Context triple: [Thutmose I, tomb, KV20]
  • A. KV20 chosen
    KV20 is an ancient Egyptian royal tomb in the Valley of the Kings, notable as one of the earliest and deepest in the necropolis and associated with Pharaoh Hatshepsut and her father Thutmose I.
  • B. KV24
    KV24 is an ancient, unfinished tomb in Egypt’s Valley of the Kings, likely dating to the New Kingdom and never used for a formal royal burial.
  • C. KV23
    KV23 is an ancient Egyptian royal tomb in the Valley of the Kings, notable as the burial place of Pharaoh Ay.
  • D. KV25
    KV25 is an unfinished ancient Egyptian royal tomb in the Valley of the Kings, likely dating to the New Kingdom period.
  • E. KV28
    KV28 is an ancient Egyptian tomb in the Valley of the Kings, likely dating to the 18th Dynasty and used for the burial of lesser-known nobles or officials.
  • 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_69d889e1c6148190ba76241e74688f8b completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46d3174008190a2b5bb1b061ea4df completed April 19, 2026, 5:50 a.m.
Created at: April 10, 2026, 5:51 a.m.