Triple
T11039229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekhemkhet |
E260964
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Khaba |
E453013
|
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: Khaba | Statement: [Sekhemkhet, successor, Khaba]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khaba Context triple: [Sekhemkhet, successor, Khaba]
-
A.
Khaba
chosen
Khaba was an early ancient Egyptian pharaoh of the 3rd Dynasty, best known for his association with the unfinished Layer Pyramid at Zawyet el'Aryan and for the relative obscurity surrounding his reign.
-
B.
Hakha
Hakha is a hill town in western Myanmar that serves as the administrative and cultural center of the Chin people.
-
C.
Khorlim
Khorlim is a village located in the North Goa district of the Indian state of Goa.
-
D.
Khashuri
Khashuri is a town in central Georgia that serves as an important regional transport hub and gateway between eastern and western parts of the country.
-
E.
Khotta
Khotta is an alternate name for the Khortha language, an Indo-Aryan language spoken primarily in the Indian state of Jharkhand.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797fe93b081909d58bfd4b42715f0 |
completed | April 9, 2026, 12:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3a9d61b548190949f0dfbcb782064 |
completed | April 18, 2026, 3:57 p.m. |
Created at: April 8, 2026, 9:26 p.m.