Triple
T30107070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huluppu tree |
E765161
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | object in Sumerian mythology |
C13638
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: object in Sumerian mythology Context triple: [Huluppu tree, instanceOf, object in Sumerian mythology]
-
A.
Mesopotamian deity
A Mesopotamian deity is a divine being from the ancient cultures of Sumer, Akkad, Assyria, and Babylonia, associated with specific cosmic, natural, or societal domains and worshiped through rituals, temples, and myths.
-
B.
Babylonian god
A Babylonian god is a divine being from ancient Mesopotamian religion, associated with specific cosmic functions, cities, or aspects of life, and worshiped through rituals, temples, and myths.
-
C.
mythological object
chosen
A mythological object is a fantastical item or artifact that appears in myths and legends, often imbued with supernatural powers or symbolic significance within a culture’s storytelling tradition.
-
D.
object in Finnish mythology
An object in Finnish mythology is a tangible or symbolic item—such as a weapon, tool, artifact, or natural feature—endowed with mythic origin, supernatural power, or cultural significance within the Finnish mythological tradition.
-
E.
Mesopotamian mythological place
A Mesopotamian mythological place is a legendary or sacred location from ancient Mesopotamian belief systems, such as heavens, underworlds, or divine cities, that features in myths, religious texts, and ritual narratives.
- F. None of above.
Provenance (1 batch)
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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:09 p.m.