Triple
T34537381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hare nome |
E886706
|
entity |
| Predicate | positionInUpperEgypt |
P199940
|
FINISHED |
| Object | 15th nome of Upper Egypt |
—
|
LITERAL 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: 15th nome of Upper Egypt | Statement: [Hare nome, positionInUpperEgypt, 15th nome of Upper Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInUpperEgypt Context triple: [Hare nome, positionInUpperEgypt, 15th nome of Upper Egypt]
-
A.
locatedInNorthernUpperEgypt
Indicates that the subject is geographically situated in the northern part of Upper Egypt.
-
B.
locatedInDirectionWithinEgypt
Indicates that one place is situated in a specified cardinal or relative direction from another place, with both locations being within the borders of Egypt.
-
C.
directionRelativeToLowerEgypt
Indicates the spatial direction of something when referenced relative to the geographic position of Lower Egypt.
-
D.
locatedOnBankOfNile
Indicates that something is situated on or directly adjacent to the banks of the Nile River.
-
E.
incorporatedIntoMakuriaBy
Indicates that one entity was absorbed or unified into the political or territorial domain of Makuria.
- F. None of above. chosen
Provenance (4 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
| PDg | Predicate description generation | batch_69ff64b864f481909fcefc2b08595c89 |
completed | May 9, 2026, 4:45 p.m. |
Created at: May 1, 2026, 2:02 a.m.