Triple
T32823320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyramid of Khentkaus I |
E839488
|
entity |
| Predicate | hasInscriptionTitle |
P85001
|
FINISHED |
| Object | Mother of two kings of Upper and Lower Egypt |
—
|
LITERAL 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: Mother of two kings of Upper and Lower Egypt | Statement: [Pyramid of Khentkaus I, hasInscriptionTitle, Mother of two kings of Upper and Lower Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInscriptionTitle Context triple: [Pyramid of Khentkaus I, hasInscriptionTitle, Mother of two kings of Upper and Lower Egypt]
-
A.
hasTitleInInscription
chosen
Indicates that an entity is mentioned with a specific title or designation within an inscription.
-
B.
hasInscriptions
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
C.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
D.
isTitled
Indicates that an entity holds or is assigned a specific formal title or designation.
-
E.
hasNameInscribed
Indicates that an entity bears another entity’s name physically inscribed on its surface.
- 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_69f3493df9008190a8f5d843dcd77704 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: May 1, 2026, 1:15 a.m.