Triple
T36284302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amenemhat V |
E893029
|
entity |
| Predicate | capitalRegionDuringReign |
P9119
|
FINISHED |
| Object | Upper Egypt |
—
|
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: Upper Egypt | Statement: [Amenemhat V, capitalRegionDuringReign, Upper Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalRegionDuringReign Context triple: [Amenemhat V, capitalRegionDuringReign, Upper Egypt]
-
A.
capitalOfRealmDuringReign
Indicates that a particular city or place served as the capital of a realm specifically during the time span of a given ruler’s reign.
-
B.
capitalDuringReign
chosen
Indicates that a particular city or location served as the capital of a political entity during the reign of a specified ruler.
-
C.
regionOfDynasty
Indicates the geographic region or area in which a given dynasty held power or was primarily based.
-
D.
namedDuringReignOf
Indicates that one entity received its name while another entity (typically a ruler or regime) was in power.
-
E.
ruledDuringReignOf
Indicates that one entity exercised ruling authority or governance during the time period in which another entity’s reign took place.
- F. None of above.
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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdd07a34c08190982b8c61c2775cf6 |
completed | May 8, 2026, noon |
| PD | Predicate disambiguation | batch_69fdbd25c7908190b72fca8de7ce503f |
completed | May 8, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:09 p.m.