Triple
T30462854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indo-Iranian mythology |
E775057
|
entity |
| Predicate | sharesMythicTheme |
P47748
|
FINISHED |
| Object | cosmic waters |
—
|
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 waters | Statement: [Indo-Iranian mythology, sharesMythicTheme, cosmic waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesMythicTheme Context triple: [Indo-Iranian mythology, sharesMythicTheme, cosmic waters]
-
A.
hasMythicTheme
Indicates that something embodies, references, or is characterized by a mythic or mythological theme.
-
B.
mythicAlliance
Indicates a cooperative or strategic partnership formed between entities within a legendary, mythical, or supernatural context.
-
C.
sharesThemeWith
chosen
Indicates that two entities are related by having the same or closely similar underlying theme or subject matter.
-
D.
sharesMythosWith
Indicates that two entities are associated with, or originate from, the same mythological tradition, narrative system, or shared set of myths.
-
E.
mysticalTheme
Indicates that the subject is associated with or characterized by mystical, supernatural, or esoteric themes.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: April 29, 2026, 8:10 p.m.