Triple
T9779112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atrahasis |
E237319
|
entity |
| Predicate | cosmicEventSurvived |
P5939
|
FINISHED |
| Object | world-destroying flood |
—
|
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: world-destroying flood | Statement: [Atrahasis, cosmicEventSurvived, world-destroying flood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicEventSurvived Context triple: [Atrahasis, cosmicEventSurvived, world-destroying flood]
-
A.
survivedEvent
chosen
Indicates that an entity continued to live or exist after experiencing and not being destroyed or killed by a particular event.
-
B.
cosmicInteraction
Indicates an interaction or influence occurring between cosmic or astronomical entities or phenomena.
-
C.
placeOfEventSurvived
Indicates the location where an event occurred from which the subject successfully survived.
-
D.
cosmicProcess
Indicates a large-scale natural phenomenon or sequence of events occurring in the universe, such as the formation, evolution, or transformation of cosmic structures.
-
E.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda13663f081909b95563038eb6485 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.