Triple
T19429213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adishesha |
E486064
|
entity |
| Predicate | mythicAttribute |
P135854
|
FINISHED |
| Object | remains after cosmic dissolution |
—
|
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: remains after cosmic dissolution | Statement: [Adishesha, mythicAttribute, remains after cosmic dissolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythicAttribute Context triple: [Adishesha, mythicAttribute, remains after cosmic dissolution]
-
A.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
B.
hasMythicMotif
Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other entity.
-
C.
isMythicPrototypeOf
Indicates that one entity serves as the mythic or legendary archetype, model, or original form upon which the other entity is based or derived.
-
D.
isMythical
Indicates that the entity is considered mythical, existing only in legend, folklore, or imagination rather than in reality.
-
E.
hasMythicSetting
Indicates that something is set within a mythic, legendary, or folklore-based world or context.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6321b78d08190b86cef7c60cbb61c |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.