Triple
T19966496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satyavrata |
E479947
|
entity |
| Predicate | rescuedDuring |
P138060
|
FINISHED |
| Object | cosmic 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: cosmic flood | Statement: [Satyavrata, rescuedDuring, cosmic flood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescuedDuring Context triple: [Satyavrata, rescuedDuring, cosmic flood]
-
A.
rescuedTo
Indicates that one entity has been saved or freed from danger, harm, or a problematic situation and brought to the safety or custody of another entity or location.
-
B.
rescuedInFormOf
Indicates that one entity is rescued, saved, or recovered specifically in the form, state, or manifestation represented by another entity.
-
C.
rescuesFrom
Indicates that one entity saves or frees another entity from a dangerous, harmful, or undesirable situation or source.
-
D.
rescuesWith
Indicates that one entity saves or frees another entity from danger, harm, or captivity using a particular means, tool, or method.
-
E.
crewRescued
Indicates that a crew has been successfully saved from danger or a threatening situation.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc5e41881908c1e8867820f1c0c |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.