Triple
T8916478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekur |
E212307
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Nippur |
E38027
|
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: Nippur | Statement: [Ekur, locatedIn, Nippur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nippur Context triple: [Ekur, locatedIn, Nippur]
-
A.
Nippur
chosen
Nippur was an ancient Sumerian city in Mesopotamia that served as a major religious center dedicated to the god Enlil.
-
B.
Sippar
Sippar was an important ancient Mesopotamian city, renowned as a religious and administrative center particularly associated with the sun god Shamash.
-
C.
Lagash
Lagash was an important ancient Sumerian city-state in southern Mesopotamia, known for its early political power, distinctive art, and extensive cuneiform records.
-
D.
Harapha
Harapha is a boastful Philistine giant who serves as Samson’s arrogant antagonist in John Milton’s tragic closet drama "Samson Agonistes."
-
E.
Erech
Erech is the ancient name for the Mesopotamian city of Uruk, one of the earliest major urban centers in human history.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6610cd48819090a184c5f9465626 |
completed | April 1, 2026, 12:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc1d0965c81908841fe591283e4a4 |
completed | April 3, 2026, 1:34 p.m. |
Created at: March 30, 2026, 6:56 p.m.