Triple
T25389066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeolian royal lineage |
E631607
|
entity |
| Predicate | timeInMythicTradition |
P20414
|
FINISHED |
| Object | Heroic Age |
—
|
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: Heroic Age | Statement: [Aeolian royal lineage, timeInMythicTradition, Heroic Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInMythicTradition Context triple: [Aeolian royal lineage, timeInMythicTradition, Heroic Age]
-
A.
timeInMyth
chosen
Indicates that an entity exists or occurs during a specific time period within a mythological narrative or tradition.
-
B.
hasMythicTimeframe
Indicates that the relationship associates something with a timeframe situated in mythic or legendary, rather than historical, time.
-
C.
timeInTradition
Indicates the temporal context or period in which a given tradition is practiced, observed, or relevant.
-
D.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
E.
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.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5656d3a04819081b3705ee9d4fd26 |
completed | May 2, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:47 p.m.