Triple
T17468367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elkab |
E425336
|
entity |
| Predicate | ancientName |
P2834
|
FINISHED |
| Object | Nekheb |
—
|
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: Nekheb | Statement: [Elkab, ancientName, Nekheb]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nekheb Context triple: [Elkab, ancientName, Nekheb]
-
A.
Nekheb
chosen
Nekheb was an ancient Egyptian city in Upper Egypt, closely associated with the vulture goddess Nekhbet and serving as an important religious and political center.
-
B.
Nakhtnebef
Nakhtnebef is the birth name of Nectanebo I, the founder of Egypt’s Thirtieth Dynasty and one of the last native Egyptian pharaohs.
-
C.
Shemu
Shemu is the ancient Egyptian season of harvest, marking the time when crops were gathered before the annual Nile inundation.
-
D.
Nebkauhor
Nebkauhor was an ancient Egyptian prince of the 6th Dynasty, known as a son of Pharaoh Teti.
-
E.
Senenmut
Senenmut was a prominent ancient Egyptian official and architect of the 18th Dynasty, best known for his close association with Pharaoh Hatshepsut and for designing some of her most famous monuments.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451aa0e1c81909627369465575c06 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 5:47 a.m.