Triple
T34959361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ankh-Merenre |
E1008209
|
entity |
| Predicate | locatedInDynasty |
P164412
|
FINISHED |
| Object | Sixth Dynasty of Egypt |
E51683
|
NE FINISHED |
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: Sixth Dynasty of Egypt | Statement: [Ankh-Merenre, locatedInDynasty, Sixth Dynasty of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInDynasty Context triple: [Ankh-Merenre, locatedInDynasty, Sixth Dynasty of Egypt]
-
A.
positionInDynasty
Indicates the specific role or rank an individual holds within a particular dynasty’s internal hierarchy.
-
B.
existedUnderDynasty
chosen
Indicates that an entity existed or was in effect during the period of a specified dynasty’s rule.
-
C.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
-
D.
partOfDynasty
Indicates that an entity belongs to, or is a constituent member of, a particular dynasty.
-
E.
veneratedInDynasty
Indicates that an entity was revered, honored, or held in high esteem during a specific historical dynasty.
- F. None of above.
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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37fafcfefc81909a7d93a98ca78e5b |
completed | June 21, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.