Triple
T20931644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keyumars |
E515484
|
entity |
| Predicate | positionInMythicHistory |
P73488
|
FINISHED |
| Object | first king of the world |
—
|
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: first king of the world | Statement: [Keyumars, positionInMythicHistory, first king of the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInMythicHistory Context triple: [Keyumars, positionInMythicHistory, first king of the world]
-
A.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
B.
positionOnMyth
Indicates the relative stance or viewpoint an entity holds regarding a particular myth.
-
C.
hasMythicTimeframe
Indicates that the relationship associates something with a timeframe situated in mythic or legendary, rather than historical, time.
-
D.
notableMythicKing
chosen
Indicates that the subject is recognized as a prominent or distinguished king within myth or legend.
-
E.
legendaryPeriod
Indicates a time span associated with legends or mythic events rather than strictly historical chronology.
- 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.