Triple
T20931700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hushang |
E515485
|
entity |
| Predicate | cosmicRoleInMyth |
P137962
|
FINISHED |
| Object | early world ruler |
—
|
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: early world ruler | Statement: [Hushang, cosmicRoleInMyth, early world ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicRoleInMyth Context triple: [Hushang, cosmicRoleInMyth, early world ruler]
-
A.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
B.
cosmicRoleInTexts
chosen
Indicates the role or function an entity is described as having within cosmic or mythological contexts in texts.
-
C.
cosmicSymbolism
Indicates a relationship where one entity symbolically represents or embodies cosmic, universal, or celestial principles in relation to another.
-
D.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
E.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f65681b4819083c7ef6b44ba4bdb |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.