Triple
T23428366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Necho I |
E563254
|
entity |
| Predicate | opponent |
P437
|
FINISHED |
| Object | Taharqa |
—
|
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: Taharqa | Statement: [Necho I, opponent, Taharqa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Taharqa Context triple: [Necho I, opponent, Taharqa]
-
A.
Taharqa
chosen
Taharqa was a prominent pharaoh of Egypt’s 25th (Kushite) Dynasty, known for his extensive building projects and resistance against Assyrian expansion in the 7th century BCE.
-
B.
Wahibre Psamtik
Wahibre Psamtik, better known as Psamtik I, was a 7th-century BCE pharaoh who reunified Egypt and founded the Saite 26th Dynasty.
-
C.
Amenemopet
Amenemopet was a royal prince of Egypt during the 20th Dynasty, known as a son of Pharaoh Ramesses IX.
-
D.
Aakheperure
Aakheperure was the throne name of the Egyptian pharaoh Amenhotep II of the 18th Dynasty.
-
E.
Nakhtnebef
Nakhtnebef is the birth name of Nectanebo I, the founder of Egypt’s Thirtieth Dynasty and one of the last native Egyptian pharaohs.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a54ba29881909945690496f28d65 |
completed | April 29, 2026, 6:29 a.m. |
Created at: April 17, 2026, 5:48 p.m.