Triple
T18763589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fussa |
E458836
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Hamura |
—
|
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: Hamura | Statement: [Fussa, borderedBy, Hamura]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hamura Context triple: [Fussa, borderedBy, Hamura]
-
A.
Hamura
chosen
Hamura is a city in western Tokyo, Japan, known for its residential neighborhoods and proximity to the Tama River.
-
B.
Ziusuddu
Ziusuddu is a legendary Sumerian figure known as the hero of an ancient Mesopotamian flood myth, often compared to the biblical Noah.
-
C.
Sinsharishkun
Sinsharishkun was one of the last kings of the Neo-Assyrian Empire, whose reign saw the empire’s collapse amid internal strife and external rebellions.
-
D.
Hammurabi
Hammurabi was the sixth king of Babylon, best known for creating one of the earliest and most influential written legal codes in ancient Mesopotamia.
-
E.
Hammurabi I of Yamkhad
Hammurabi I of Yamkhad was a prominent Amorite king of the ancient Syrian city-state of Aleppo, known for expanding its power and influence in the early second millennium BCE.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d80a954819083946dafc0c7af05 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 10, 2026, 11:52 a.m.