Triple
T30706331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akkadian period |
E781762
|
entity |
| Predicate | hasMajorPower |
P544
|
FINISHED |
| Object | Akkadian Empire |
—
|
NE NERFINISHED |
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: Akkadian Empire | Statement: [Akkadian period, hasMajorPower, Akkadian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorPower Context triple: [Akkadian period, hasMajorPower, Akkadian Empire]
-
A.
hasPowerful
Indicates that one entity possesses significant strength, influence, or capability relative to another entity or context.
-
B.
hasPower
chosen
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
hasMajor
Indicates that an entity (typically a person or student) has a specific primary field of academic study or specialization.
-
D.
majorPowerUntil
Indicates that an entity functioned as a major power or dominant force up to, but not beyond, a specified time or event.
-
E.
madeMajorPower
Indicates that one entity caused or enabled another entity to attain the status or influence of a major power.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: April 29, 2026, 8:35 p.m.