Triple
T26653480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Causeway of Khafre |
E666430
|
entity |
| Predicate | pharaohReign |
P161091
|
FINISHED |
| Object | reign of Khafre |
—
|
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: reign of Khafre | Statement: [Causeway of Khafre, pharaohReign, reign of Khafre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pharaohReign Context triple: [Causeway of Khafre, pharaohReign, reign of Khafre]
-
A.
majorPharaoh
Indicates that the subject is recognized as a principal or highly significant pharaoh in relation to the object (such as a period, dynasty, or context).
-
B.
lastPharaoh
Indicates that the subject is the final individual to have held the position or role of pharaoh in a given context.
-
C.
lastNativePharaohBefore
Indicates that one person was the final pharaoh of native origin to rule before another specified ruler or ruling group took power.
-
D.
dynastyRuled
Indicates that a particular dynasty held ruling authority or governance over a specified region, state, or people during a certain period.
-
E.
associatedDynastyRuler
Indicates a relationship where a dynasty is linked to the ruler who governed or is historically connected with it.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6167ccb308190a3183b2145bf4ce8 |
completed | May 2, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 2:34 a.m.