Triple
T30706330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akkadian period |
E781762
|
entity |
| Predicate | hasPrecededByRuler |
P135815
|
FINISHED |
| Object | Sargon of Akkad |
—
|
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: Sargon of Akkad | Statement: [Akkadian period, hasPrecededByRuler, Sargon of Akkad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrecededByRuler Context triple: [Akkadian period, hasPrecededByRuler, Sargon of Akkad]
-
A.
hasFirstRuler
Indicates that an entity has another entity as its earliest or original ruler.
-
B.
hasLastRuler
Indicates that a specified entity is the final or most recent ruler of another entity (such as a state, dynasty, or territory).
-
C.
hasRulerProclaimed
Indicates that a ruler has formally announced, declared, or publicly proclaimed something.
-
D.
predecessorAsLocalRuler
chosen
Indicates that one entity previously held the position of local ruler immediately before another entity in a given domain or territory.
-
E.
hasFormerRuler
Indicates that an entity previously served as the ruler of another entity but no longer holds that ruling position.
- 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_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: April 29, 2026, 8:35 p.m.