Triple
T31421793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ur-Nammu |
E801549
|
entity |
| Predicate | codeDate |
P118762
|
FINISHED |
| Object | circa 2100–2050 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 2100–2050 BCE | Statement: [Ur-Nammu, codeDate, circa 2100–2050 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeDate Context triple: [Ur-Nammu, codeDate, circa 2100–2050 BCE]
-
A.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
B.
developmentDate
chosen
Indicates the date on which something was created, developed, or brought into existence.
-
C.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
D.
titleDate
Indicates the date associated with a title, such as when it was granted, recorded, or became effective.
-
E.
dateImplemented
Indicates the date on which something (such as a plan, rule, feature, or system) was put into effect or made operational.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:49 p.m.