Triple
T37889714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sewadjkare XVII |
E945093
|
entity |
| Predicate | geographicalRegionRuled |
P44467
|
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: [Sewadjkare XVII, geographicalRegionRuled, Upper Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicalRegionRuled Context triple: [Sewadjkare XVII, geographicalRegionRuled, Upper Egypt]
-
A.
historicalRegionGoverned
chosen
Indicates that a subject entity exercised governing authority over a particular historical region during a specified period.
-
B.
countryRuled
Indicates that one entity exercises governing authority or political control over a country.
-
C.
regionOfDynasty
Indicates the geographic region or area in which a given dynasty held power or was primarily based.
-
D.
historicalRegionOfInfluence
Indicates that one entity was historically within the geographic, political, or cultural sphere of influence of another entity.
-
E.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: May 3, 2026, 4:19 p.m.