Triple
T35173014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sewadjkare XLV |
E1015600
|
entity |
| Predicate | periodFollowedBy |
P57700
|
FINISHED |
| Object | Hyksos domination in northern 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: Hyksos domination in northern Egypt | Statement: [Sewadjkare XLV, periodFollowedBy, Hyksos domination in northern Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: periodFollowedBy Context triple: [Sewadjkare XLV, periodFollowedBy, Hyksos domination in northern Egypt]
-
A.
followedByPeriod
chosen
Indicates that one event, state, or item is immediately succeeded in time or sequence by a subsequent period.
-
B.
endedFollowing
Indicates that one entity stopped following or subscribing to another entity after previously doing so.
-
C.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
D.
eraFollowed
Indicates that one historical era comes directly after another in chronological sequence.
-
E.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
- 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_69f76ddcc108819097f96853b7ed9ef4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:02 p.m.