Triple
T30168504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akkadian literature |
E766856
|
entity |
| Predicate | bestKnownWork |
P4
|
FINISHED |
| Object | Epic of Gilgamesh |
—
|
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: Epic of Gilgamesh | Statement: [Akkadian literature, bestKnownWork, Epic of Gilgamesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestKnownWork Context triple: [Akkadian literature, bestKnownWork, Epic of Gilgamesh]
-
A.
notableWorkIn
Indicates that an entity is known for or associated with a significant work, contribution, or achievement in a particular field or context.
-
B.
notableWork
chosen
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
C.
notableTypeOfWork
Indicates that a work is a significant or defining example within a particular type or category of work associated with an entity.
-
D.
notableWorkAs
Indicates a relationship where a particular work is recognized as a significant or distinguished creation associated with an entity.
-
E.
labelOfNotableWork
Indicates that the object is the title or label of a notable work associated with the subject.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f0951288190a809554f58be124f |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:23 p.m.