Triple
T24185088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Solomon |
E599534
|
entity |
| Predicate | dynasticRestoration |
P20221
|
FINISHED |
| Object | Yekuno Amlak |
—
|
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: Yekuno Amlak | Statement: [House of Solomon, dynasticRestoration, Yekuno Amlak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticRestoration Context triple: [House of Solomon, dynasticRestoration, Yekuno Amlak]
-
A.
dynastyRestored
chosen
Indicates that a previously displaced ruling dynasty has been returned to power or reestablished as the legitimate authority.
-
B.
dynasticRight
Indicates a hereditary claim or entitlement to rule or hold authority based on lineage within a dynasty.
-
C.
dynasticState
Indicates a relationship where a state or political entity is ruled or defined by a hereditary dynasty or ruling family.
-
D.
dynasticDomain
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
-
E.
reconstructionDynasty
Indicates that one dynasty is a reconstruction, restoration, or reestablished form of another dynasty.
- 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_69e288cdc8b88190bf2f835d3cb4ca28 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:35 p.m.