Triple
T27381382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khasekhemwy |
E691238
|
entity |
| Predicate | earlierNameMeaning |
P83314
|
FINISHED |
| Object | The Powerful One Appears |
—
|
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: The Powerful One Appears | Statement: [Khasekhemwy, earlierNameMeaning, The Powerful One Appears]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierNameMeaning Context triple: [Khasekhemwy, earlierNameMeaning, The Powerful One Appears]
-
A.
formerNameMeaning
chosen
Indicates that the meaning or interpretation of an entity’s previous name is being specified.
-
B.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
C.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
-
D.
ancientNameMeaning
Indicates that an entity’s ancient or historical name carries a particular meaning or interpretation.
-
E.
originalNameMeaningSource
Indicates that there is a source or reference that explains or provides the meaning of an entity’s original name.
- 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_69ef52022538819081f873d0c84a6dd6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 12:22 p.m.