Triple
T14781475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amel-Marduk |
E347398
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Kashshaya |
E347398
|
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: Kashshaya | Statement: [Amel-Marduk, spouse, Kashshaya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kashshaya Context triple: [Amel-Marduk, spouse, Kashshaya]
-
A.
Kashshaya
chosen
Kashshaya was a Neo-Babylonian royal woman known primarily as the wife of King Amel-Marduk.
-
B.
Kashira
Kashira is a historic town in Russia, located south of Moscow on the Oka River and known as a regional industrial and transport center.
-
C.
Kashenyi
Kashenyi is a town in western Uganda that serves as one of the main urban centers in Rubirizi District.
-
D.
Kasari
Kasari is a town located on Amami Ōshima in Japan’s Kagoshima Prefecture, known for its subtropical island scenery and coastal environment.
-
E.
Kaei
Kaei was a Japanese era name (nengō) of the late Edo period, notable for encompassing events such as the arrival of Commodore Perry and the opening of Japan to the West.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deca9de3f48190b7706925e2947cf5 |
completed | April 14, 2026, 11:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0d02e28081909a11d6e6fdb8d28c |
completed | May 8, 2026, 4:19 p.m. |
Created at: April 10, 2026, 1:31 a.m.