Triple
T30790060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enshakushanna |
E784067
|
entity |
| Predicate | reignApproximateDate |
P174272
|
FINISHED |
| Object | circa 25th 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: circa 25th century BCE | Statement: [Enshakushanna, reignApproximateDate, circa 25th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignApproximateDate Context triple: [Enshakushanna, reignApproximateDate, circa 25th century BCE]
-
A.
reignApproximateDates
chosen
Indicates that the time period associated with a ruler’s reign is known only approximately, rather than with precise start and end dates.
-
B.
reignedFrom
Indicates the time period during which an entity held ruling authority or sovereignty over a domain.
-
C.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
D.
yearOfReign
Indicates the specific year or span of years during which a ruler or authority held official power or reigned.
-
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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 8:41 p.m.