Triple
T9075201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eannatum |
E217465
|
entity |
| Predicate | assertedControlOver |
P67931
|
FINISHED |
| Object | canal and boundary region between Lagash and Umma |
—
|
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: canal and boundary region between Lagash and Umma | Statement: [Eannatum, assertedControlOver, canal and boundary region between Lagash and Umma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assertedControlOver Context triple: [Eannatum, assertedControlOver, canal and boundary region between Lagash and Umma]
-
A.
assertedControlBy
Indicates that one entity has taken or claimed authoritative power or dominance over another entity, typically through deliberate action or declaration.
-
B.
assertedPower
chosen
Indicates that one entity has claimed, declared, or exercised authority, control, or dominance over another entity or domain.
-
C.
aimsToControl
Indicates an intention or effort by one entity to gain power over, direct, or regulate another entity or situation.
-
D.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
E.
recognizedControlOf
Indicates that one entity has formally acknowledged and accepted another entity’s authority or control over something.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc95c4026c8190b553aedb9f4beabb |
completed | April 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:12 p.m.