Triple
T18694080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uta-napišti |
E457070
|
entity |
| Predicate | reasonForImmortality |
P132314
|
FINISHED |
| Object | surviving the great deluge |
—
|
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: surviving the great deluge | Statement: [Uta-napišti, reasonForImmortality, surviving the great deluge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForImmortality Context triple: [Uta-napišti, reasonForImmortality, surviving the great deluge]
-
A.
causeOfImmortality
Indicates that the subject is the reason or source for the object's immortality.
-
B.
immortality
Indicates that an entity possesses the quality of never dying or ceasing to exist, persisting indefinitely through time.
-
C.
ruleOfImmortals
Indicates a governing or authoritative relationship exercised by immortal beings over others.
-
D.
notImmortal
Indicates that the entity does not possess immortality and is subject to death or an end to its existence.
-
E.
reasonForTribute
Indicates the underlying cause, justification, or circumstance that explains why a tribute is given.
- 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_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. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:49 a.m.