Triple
T30529951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shuruppak |
E776966
|
entity |
| Predicate | traditionalLastKingBeforeFlood |
P195683
|
FINISHED |
| Object | Utnapishtim |
—
|
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: Utnapishtim | Statement: [Shuruppak, traditionalLastKingBeforeFlood, Utnapishtim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalLastKingBeforeFlood Context triple: [Shuruppak, traditionalLastKingBeforeFlood, Utnapishtim]
-
A.
lastKingBeforeStewards
Indicates that one entity is the final king who ruled immediately prior to the period when stewards assumed governing authority over the other entity.
-
B.
lastDukeBeforeKingship
Indicates that the subject was the final holder of the ducal title immediately prior to the establishment or assumption of kingship.
-
C.
lastRulingKingdom
Indicates that one entity is the final or most recent kingdom to have ruled over the other entity.
-
D.
mostPowerfulKing
Indicates that the subject is the king who holds the greatest power or authority among a specified group of kings.
-
E.
hadKingdom
Indicates that an entity possessed or ruled over a particular kingdom.
- F. None of above. chosen
Provenance (4 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_69f2249c11508190ae7e955755ccfb01 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
| PDg | Predicate description generation | batch_69fddf70ab10819088b76bd98e208354 |
completed | May 8, 2026, 1:04 p.m. |
Created at: April 29, 2026, 8:18 p.m.