Triple
T27265440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kheperkare |
E687887
|
entity |
| Predicate | linkedRulerReignEnd |
P2721
|
FINISHED |
| Object | 362 BC |
—
|
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: 362 BC | Statement: [Kheperkare, linkedRulerReignEnd, 362 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedRulerReignEnd Context triple: [Kheperkare, linkedRulerReignEnd, 362 BC]
-
A.
latestReignEnd
Indicates the date or time when the most recent reign or period of rule by an entity came to an end.
-
B.
endOfReign
chosen
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
C.
ended reign start year
Indicates the calendar year in which a ruler’s period of reign came to an end.
-
D.
reignApproximateDates
Indicates that the time period associated with a ruler’s reign is known only approximately, rather than with precise start and end dates.
-
E.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 27, 2026, 10:55 a.m.