Triple
T16075892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wadi al-Muluk |
E389977
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | KV57 |
E403796
|
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: KV57 | Statement: [Wadi al-Muluk, contains, KV57]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KV57 Context triple: [Wadi al-Muluk, contains, KV57]
-
A.
KV57
chosen
KV57 is the rock-cut tomb in Egypt’s Valley of the Kings built for Pharaoh Horemheb of the late 18th Dynasty, notable for its transitional art and well-preserved reliefs.
-
B.
KV59
KV59 is an unfinished and undecorated ancient Egyptian tomb in the Valley of the Kings whose owner remains unknown.
-
C.
KV53
KV53 is an ancient Egyptian tomb located in the West Valley of the Valley of the Kings near Luxor.
-
D.
KV56
KV56 is an ancient Egyptian tomb in the Valley of the Kings, notable for its rich cache of jewelry and artifacts dating to the late 19th Dynasty.
-
E.
KV55
KV55 is an enigmatic New Kingdom royal tomb in Egypt’s Valley of the Kings, notable for its controversial, still-debated occupant linked to the Amarna period.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e183c27aac81909c56d200c0c51a0c |
completed | April 17, 2026, 12:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00606a3d5c8190a145ca35ce458f7e |
completed | May 10, 2026, 10:39 a.m. |
Created at: April 10, 2026, 4:57 a.m.