Triple
T37689537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspelta |
E938465
|
entity |
| Predicate | contemporaryEgyptianKing |
P170650
|
FINISHED |
| Object | Psamtik II |
—
|
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: Psamtik II | Statement: [Aspelta, contemporaryEgyptianKing, Psamtik II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryEgyptianKing Context triple: [Aspelta, contemporaryEgyptianKing, Psamtik II]
-
A.
contemporaryEgyptianDynasty
Indicates that two Egyptian dynasties existed during the same historical time period or overlapped significantly in time.
-
B.
contemporaryRuler
chosen
Indicates that two rulers held power during overlapping or the same historical time period.
-
C.
majorPharaoh
Indicates that the subject is recognized as a principal or highly significant pharaoh in relation to the object (such as a period, dynasty, or context).
-
D.
lastPharaoh
Indicates that the subject is the final individual to have held the position or role of pharaoh in a given context.
-
E.
pharaohReign
Indicates that a specified individual ruled as pharaoh over a particular realm during a given time 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
Created at: May 3, 2026, 4:18 p.m.