Triple
T37689536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspelta |
E938465
|
entity |
| Predicate | contemporaryEgyptianDynasty |
P192538
|
FINISHED |
| Object | 26th Dynasty of 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: 26th Dynasty of Egypt | Statement: [Aspelta, contemporaryEgyptianDynasty, 26th Dynasty of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contemporaryEgyptianDynasty Context triple: [Aspelta, contemporaryEgyptianDynasty, 26th Dynasty of Egypt]
-
A.
currentDynastyFoundedYear
Indicates the year in which the currently ruling dynasty was established or came into power.
-
B.
hasFirstDynasty
Indicates that an entity is associated with or ruled by a specified first (earliest) dynasty in a given succession or historical sequence.
-
C.
secondDynasty
Indicates that an entity belongs to, is associated with, or occurred during the second dynasty in a given dynastic sequence.
-
D.
pharaohReign
Indicates that a specified individual ruled as pharaoh over a particular realm during a given time period.
-
E.
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).
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69fd0d0aebac8190868a7714ddb4f1fd |
completed | May 7, 2026, 10:07 p.m. |
Created at: May 3, 2026, 4:18 p.m.