Triple
T9075183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eannatum |
E217465
|
entity |
| Predicate | conflictWith |
P4897
|
FINISHED |
| Object | Kish |
E212532
|
NE 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: Kish | Statement: [Eannatum, conflictWith, Kish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kish Context triple: [Eannatum, conflictWith, Kish]
-
A.
Kish
chosen
Kish was an important ancient Sumerian city-state in Mesopotamia, often associated with early kingship traditions and political power in the region.
-
B.
Kish
Kish is a Benjaminite figure in the Hebrew Bible best known as the father of Israel’s first king, Saul.
-
C.
Kish
Kish is a popular Iranian resort island in the Persian Gulf, known for its free-trade zone status, beaches, and tourism facilities.
-
D.
Kishar
Kishar is a primordial Mesopotamian earth goddess associated with the horizon and paired with the sky god Anshar in ancient creation myths.
-
E.
Hirapa
Hirapa is a popular amusement park in Hirakata, Osaka, Japan, known for its variety of rides, seasonal events, and family-friendly attractions.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffdfe16c4819092c884bc3fe5daeb |
completed | April 3, 2026, 5:50 p.m. |
Created at: March 30, 2026, 7:12 p.m.