Triple
T20226092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beni Hasan |
E495382
|
entity |
| Predicate | associatedWithAdministrativeUnit |
P3892
|
FINISHED |
| Object | Oryx nome (16th Upper Egyptian nome) |
—
|
NE NERFINISHED |
How this triple was built (3 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: Oryx nome (16th Upper Egyptian nome) | Statement: [Beni Hasan, associatedWithAdministrativeUnit, Oryx nome (16th Upper Egyptian nome)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oryx nome (16th Upper Egyptian nome) Context triple: [Beni Hasan, associatedWithAdministrativeUnit, Oryx nome (16th Upper Egyptian nome)]
-
A.
Sixth Upper Egyptian nome
The Sixth Upper Egyptian nome was an ancient administrative district of Upper Egypt, centered around the city of Iunet (modern Dendera), an important religious and regional hub.
-
B.
Nome of Upper Egypt
The Nome of Upper Egypt was an ancient Egyptian administrative district in the southern Nile Valley, encompassing cities such as Lycopolis and governed by local officials under the pharaonic state.
-
C.
Upper Egyptian nome system
The Upper Egyptian nome system was an ancient administrative and territorial division of Upper Egypt into regional districts (nomes), each governed by local officials and used for political, economic, and religious organization.
-
D.
Theban nome
The Theban nome was an ancient administrative district of Upper Egypt centered on the powerful religious and political city of Thebes (Waset).
-
E.
Said (Upper Egypt)
Said (Upper Egypt) is the southern, historically significant region of Egypt along the Nile, known for its ancient cities, distinct cultural traditions, and role as the heartland of Pharaonic civilization.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Oryx nome (16th Upper Egyptian nome) Target entity description: The Oryx nome was the 16th administrative district of Upper Egypt in ancient times, centered around the region of Beni Hasan and known for its rock-cut tombs and local governors.
-
A.
Sixth Upper Egyptian nome
The Sixth Upper Egyptian nome was an ancient administrative district of Upper Egypt, centered around the city of Iunet (modern Dendera), an important religious and regional hub.
-
B.
Nome of Upper Egypt
The Nome of Upper Egypt was an ancient Egyptian administrative district in the southern Nile Valley, encompassing cities such as Lycopolis and governed by local officials under the pharaonic state.
-
C.
Upper Egyptian nome system
The Upper Egyptian nome system was an ancient administrative and territorial division of Upper Egypt into regional districts (nomes), each governed by local officials and used for political, economic, and religious organization.
-
D.
Theban nome
The Theban nome was an ancient administrative district of Upper Egypt centered on the powerful religious and political city of Thebes (Waset).
-
E.
Said (Upper Egypt)
Said (Upper Egypt) is the southern, historically significant region of Egypt along the Nile, known for its ancient cities, distinct cultural traditions, and role as the heartland of Pharaonic civilization.
- F. None of above. chosen
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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd9c1f4819092a98f5fa84fb795 |
completed | April 20, 2026, 6:26 p.m. |
Created at: April 11, 2026, 11:39 p.m.