Triple
T30726234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rider |
E782285
|
entity |
| Predicate | deathSceneOpponent |
P174419
|
FINISHED |
| Object | 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: Gilgamesh | Statement: [Rider, deathSceneOpponent, Gilgamesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deathSceneOpponent Context triple: [Rider, deathSceneOpponent, Gilgamesh]
-
A.
deathSceneWork
Indicates that a creative work features or depicts the scene in which a character dies.
-
B.
deathSceneFeature
Indicates that a particular feature, element, or characteristic is present in the scene depicting a character’s death.
-
C.
deathSceneQuote
Indicates that the quoted text is spoken or presented during a character’s death scene.
-
D.
deathBy
Indicates a relationship where one entity’s death is caused by another entity, event, or factor.
-
E.
deathDescribedBy
Indicates that a death event is documented, characterized, or explained by a specific description or source.
- F. None of above. chosen
Provenance (4 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 29, 2026, 8:36 p.m.