Triple
T28218976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runaway Horses |
E711396
|
entity |
| Predicate | hasTetralogyTheme |
P76865
|
FINISHED |
| Object | cyclical reincarnation |
—
|
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: cyclical reincarnation | Statement: [Runaway Horses, hasTetralogyTheme, cyclical reincarnation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTetralogyTheme Context triple: [Runaway Horses, hasTetralogyTheme, cyclical reincarnation]
-
A.
hasTympanumTheme
Indicates that a subject features a specific thematic or narrative motif depicted in its tympanum (the semi-circular or triangular decorative space above a doorway or entrance).
-
B.
hadThemeElement
Indicates that an entity includes, involves, or is characterized by a specific thematic element as part of its overall theme.
-
C.
hasThemeInStory
chosen
Indicates that a particular theme is present or plays a significant role within a given story.
-
D.
hasFamilyTheme
Indicates that something involves, centers on, or prominently features themes related to family relationships or family life.
-
E.
hasHeroicTheme
Indicates that something (such as a work, scene, or motif) embodies or prominently features a heroic theme or quality.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 10:45 p.m.