Triple
T9662104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siduri |
E233613
|
entity |
| Predicate | roleInEpicOfGilgamesh |
P9987
|
FINISHED |
| Object | offers counsel to Gilgamesh |
—
|
LITERAL 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: offers counsel to Gilgamesh | Statement: [Siduri, roleInEpicOfGilgamesh, offers counsel to Gilgamesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInEpicOfGilgamesh Context triple: [Siduri, roleInEpicOfGilgamesh, offers counsel to Gilgamesh]
-
A.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
B.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
C.
biblicalFigureRole
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
D.
roleInStories
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
E.
roleInTheWrathOfGod
Indicates that an entity has a specific role or participation in the event, concept, or narrative referred to as "the Wrath of God."
- F. None of above.
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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0b7728819099473f404382b26a |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:14 p.m.