Triple
T15703348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shamshi-Adad I |
E380647
|
entity |
| Predicate | expandedPowerAcross |
P9117
|
FINISHED |
| Object | northern Mesopotamia |
—
|
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: northern Mesopotamia | Statement: [Shamshi-Adad I, expandedPowerAcross, northern Mesopotamia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedPowerAcross Context triple: [Shamshi-Adad I, expandedPowerAcross, northern Mesopotamia]
-
A.
expandedPowerTo
Indicates that one entity has increased or broadened authority, influence, or control over another entity or domain.
-
B.
expandedAcross
chosen
Indicates that something has grown or extended so that it now spans or covers multiple areas, regions, or segments.
-
C.
expandsPowersOf
Indicates that one entity increases, extends, or enhances the authority, capabilities, or influence held by another entity.
-
D.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
E.
expandedAs
Indicates that one entity is a more detailed, elaborated, or fully written-out form of another, capturing how the latter is expanded from the former.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.