Triple
T30169358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larak |
E766875
|
entity |
| Predicate | roleInSumerianKingList |
P91989
|
FINISHED |
| Object | early center of kingship |
—
|
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: early center of kingship | Statement: [Larak, roleInSumerianKingList, early center of kingship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSumerianKingList Context triple: [Larak, roleInSumerianKingList, early center of kingship]
-
A.
hasRoleInAncientMesopotamia
chosen
Indicates that an entity held a specific social, political, religious, or occupational role within the context of ancient Mesopotamian society.
-
B.
nameInSumerian
Indicates that an entity is known or referred to by a specific name in the Sumerian language.
-
C.
nameInSaqqaraKingList
Indicates that an entity is recorded by name in the Saqqara King List.
-
D.
roleInMonarchyPeriod
Indicates that an entity held a specific role or position during a defined period of a monarchy.
-
E.
rulerDeity
Indicates that a deity holds supreme governing or sovereign authority over a realm, people, or cosmic domain.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: April 29, 2026, 7:24 p.m.