Triple
T22040570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Scorpion |
E544626
|
entity |
| Predicate | reignDateApprox |
P112293
|
FINISHED |
| Object | late 32nd century 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: late 32nd century BCE | Statement: [King Scorpion, reignDateApprox, late 32nd century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignDateApprox Context triple: [King Scorpion, reignDateApprox, late 32nd century BCE]
-
A.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
-
B.
yearOfReign
Indicates the specific year or span of years during which a ruler or authority held official power or reigned.
-
C.
reignDuration
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
D.
centuryOfReign
chosen
Indicates the century during which a given entity’s reign or rule took place.
-
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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12828fc788190a22c0e9c2372656b |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.