Triple
T16619953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KV57 |
E403796
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | KV58 |
E1212137
|
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: KV58 | Statement: [KV57, near, KV58]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KV58 Context triple: [KV57, near, KV58]
-
A.
KV58
chosen
KV58 is a small, unfinished New Kingdom tomb in the Valley of the Kings best known for yielding a cache of royal artifacts linked to Tutankhamun and Ay.
-
B.
KV59
KV59 is an unfinished and undecorated ancient Egyptian tomb in the Valley of the Kings whose owner remains unknown.
-
C.
KV57
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.
-
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.
KV53
KV53 is an ancient Egyptian tomb located in the West Valley of the Valley of the Kings near Luxor.
- 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3754c934c8190a0a8ddd747681aa7 |
completed | April 18, 2026, 12:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0084b5afc081908d16f0b43fff20fc |
completed | May 10, 2026, 1:14 p.m. |
Created at: April 10, 2026, 5:17 a.m.