Triple
T32038712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neferu |
E818163
|
entity |
| Predicate | hasNameBearersInDynasty |
P196832
|
FINISHED |
| Object | 11th 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: 11th Dynasty of Egypt | Statement: [Neferu, hasNameBearersInDynasty, 11th Dynasty of Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameBearersInDynasty Context triple: [Neferu, hasNameBearersInDynasty, 11th Dynasty of Egypt]
-
A.
hasBranchOfImperialFamily
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
-
B.
hasSurnameBearer
Indicates that a particular surname is borne or carried by a specific person or entity.
-
C.
dynasticSurname
Indicates that the two entities share a family name associated with a particular dynasty or ruling lineage.
-
D.
rankWithinImperialFamily
Indicates the hierarchical position an individual holds within an imperial family relative to other family members.
-
E.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
| PDg | Predicate description generation | batch_69fe6b7a823881909dc2037fe25bea24 |
completed | May 8, 2026, 11:02 p.m. |
Created at: May 1, 2026, 12:19 a.m.