Triple
T10062124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mykerinos |
E213015
|
entity |
| Predicate | hasReignEstimatedStart |
P1506
|
FINISHED |
| Object | circa 2530 BCE |
—
|
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: circa 2530 BCE | Statement: [Mykerinos, hasReignEstimatedStart, circa 2530 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReignEstimatedStart Context triple: [Mykerinos, hasReignEstimatedStart, circa 2530 BCE]
-
A.
ended reign start year
Indicates the calendar year in which a ruler’s period of reign came to an end.
-
B.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
C.
hasUncertainReignLength
Indicates that the duration of an entity's reign is not known precisely or is subject to doubt or conflicting information.
-
D.
hasDynastyFounded
Indicates that an entity is the founder or originator of a particular dynasty.
-
E.
originatedInReignOf
Indicates that something began, was initiated, or first came into existence during the rule or governing period of a particular ruler or authority.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcfd3c6bc8190a21ed3566f9c08d1 |
completed | April 2, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:58 p.m.