Triple
T4783328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iravan |
E106416
|
entity |
| Predicate | hasMythRole |
P49015
|
FINISHED |
| Object | protector of devotees |
—
|
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: protector of devotees | Statement: [Iravan, hasMythRole, protector of devotees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMythRole Context triple: [Iravan, hasMythRole, protector of devotees]
-
A.
hasMythType
Indicates that an entity is associated with or classified under a particular type or category of myth.
-
B.
hasMythicFunction
chosen
Indicates that something serves a symbolic, narrative, or ritual role within a mythic or mythological framework.
-
C.
hasMythicMotif
Indicates that one entity features, embodies, or is associated with a particular mythic motif found in the other entity.
-
D.
hasMythicTheme
Indicates that something embodies, references, or is characterized by a mythic or mythological theme.
-
E.
hasMythicEvent
Indicates that an entity is associated with, involves, or features a significant mythic or legendary event.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.