Triple
T30790089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enshakushanna |
E784067
|
entity |
| Predicate | governedPolity |
P98499
|
FINISHED |
| Object | city-state of Uruk |
—
|
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: city-state of Uruk | Statement: [Enshakushanna, governedPolity, city-state of Uruk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedPolity Context triple: [Enshakushanna, governedPolity, city-state of Uruk]
-
A.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
-
B.
areGovernedBy
chosen
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
C.
hasPolity
Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
-
D.
typeOfPolity
Indicates that one entity is a political unit and the other specifies the kind or classification of that polity (e.g., empire, kingdom, republic).
-
E.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
- 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_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: April 29, 2026, 8:41 p.m.