Triple
T31088117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ur-Ningirsu II |
E792303
|
entity |
| Predicate | madeDedicationsTo |
P24360
|
FINISHED |
| Object | Sumerian deities |
—
|
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: Sumerian deities | Statement: [Ur-Ningirsu II, madeDedicationsTo, Sumerian deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeDedicationsTo Context triple: [Ur-Ningirsu II, madeDedicationsTo, Sumerian deities]
-
A.
dedicationBy
Indicates that one entity formally dedicates, commits, or devotes another entity (such as a work, resource, or effort) to a particular person, purpose, or cause.
-
B.
usedAsDedicationFor
Indicates that something (such as a work, object, or act) is dedicated in honor of, or specifically intended for, another entity.
-
C.
dedicationMessage
Indicates that one entity expresses a formal dedication or tribute message directed toward another entity or purpose.
-
D.
dedicatee
chosen
Indicates the person or entity to whom a work, such as a book, artwork, or performance, is formally dedicated.
-
E.
dedicationType
Indicates the specific kind or category of dedication that characterizes the relationship or action between entities.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:02 p.m.