Triple
T35013875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bosmeri pantheon |
E1010000
|
entity |
| Predicate | hasDaedricAspect |
P73550
|
FINISHED |
| Object | Hircine as patron of the Wild Hunt |
—
|
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: Hircine as patron of the Wild Hunt | Statement: [Bosmeri pantheon, hasDaedricAspect, Hircine as patron of the Wild Hunt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDaedricAspect Context triple: [Bosmeri pantheon, hasDaedricAspect, Hircine as patron of the Wild Hunt]
-
A.
hasDeityAspect
chosen
Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another deity.
-
B.
enchantedAs
Indicates that one entity has been placed under a magical spell or charm by another entity or force.
-
C.
hasMythicAncestor
Indicates that an entity is descended from, or claims lineage through, a figure from myth or legend.
-
D.
wrathfulAspectOf
Indicates that one entity is a fierce, anger-driven or punitive manifestation or form of another entity.
-
E.
hasRitualFocus
Indicates that an entity is associated with or directed toward a particular object, practice, or element that serves as the central focus of a ritual.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.