Triple
T24209516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qaa |
E600491
|
entity |
| Predicate | isLastRulerOf |
P1546
|
FINISHED |
| Object | First 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: First Dynasty of Egypt | Statement: [Qaa, isLastRulerOf, First Dynasty of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLastRulerOf Context triple: [Qaa, isLastRulerOf, First Dynasty of Egypt]
-
A.
lastMonarchOf
chosen
Indicates that one entity is the final reigning monarch of another entity, such as a country, kingdom, or territory.
-
B.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
C.
penultimateMonarchOf
Indicates that one entity is the second-to-last monarch to have ruled over the other entity.
-
D.
fatherIsRulerOf
Indicates that the person who is the father holds the position of ruler or sovereign over the specified entity or domain.
-
E.
finalEmperorOf
Indicates that one entity is the last ruler to hold the imperial title over another entity (such as a state, dynasty, or empire).
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f282020a5881909df47f766c3ee7af |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:53 p.m.