Triple
T25076790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloodline |
E628070
|
entity |
| Predicate | featuresSeriesMythology |
P9595
|
FINISHED |
| Object | The Otherness |
—
|
NE NERFINISHED |
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: The Otherness | Statement: [Bloodline, featuresSeriesMythology, The Otherness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSeriesMythology Context triple: [Bloodline, featuresSeriesMythology, The Otherness]
-
A.
mythologicalContent
Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
-
B.
mythologicalFigureFeatured
Indicates that a mythological figure is prominently depicted, referenced, or plays a significant role within a given work, context, or medium.
-
C.
mythologicalCategory
Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
-
D.
subsequentMythology
Indicates that one mythology develops later than, or is derived from, another mythology in time or tradition.
-
E.
linkedToMythology
chosen
Indicates that something has a connection or association with a mythological tradition, figure, story, or theme.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 18, 2026, 6:21 a.m.