Triple
T18694135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ziusudra |
E457071
|
entity |
| Predicate | afterTheFlood |
P48782
|
FINISHED |
| Object | offered sacrifice to the gods |
—
|
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: offered sacrifice to the gods | Statement: [Ziusudra, afterTheFlood, offered sacrifice to the gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterTheFlood Context triple: [Ziusudra, afterTheFlood, offered sacrifice to the gods]
-
A.
aftermathOfCreation
Indicates the state, condition, or consequences that exist as a direct result of a prior act of creation.
-
B.
afterAD
Indicates that one event, action, or state occurs later in time than another, serving as its temporal successor.
-
C.
disasterDepicted
Indicates that one entity visually represents or portrays a disaster involving or affecting another entity.
-
D.
aftermathOf
chosen
Indicates that one event, state, or condition occurs as a consequence or result following another event.
-
E.
aftermathDescription
Indicates the description or characterization of events, conditions, or consequences that occur following a particular incident or action.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562e581f48190997d279296a31e7f |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.