Triple
T20515239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoori |
E503667
|
entity |
| Predicate | inMythCycle |
P54299
|
FINISHED |
| Object | myths of the imperial lineage |
—
|
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: myths of the imperial lineage | Statement: [Hoori, inMythCycle, myths of the imperial lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inMythCycle Context triple: [Hoori, inMythCycle, myths of the imperial lineage]
-
A.
subsequentMythology
Indicates that one mythology develops later than, or is derived from, another mythology in time or tradition.
-
B.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
C.
eraOfMyth
Indicates a temporal relationship where an event, story, or phenomenon belongs to or takes place during a mythological or legendary era.
-
D.
mythologicalCategory
chosen
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
E.
originMyth
Indicates the traditional myth or legendary narrative that explains the beginnings or creation of a people, place, institution, or phenomenon.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f4133048190abb777be4b65c2c4 |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.