Triple
T20456599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legends of Shannara |
E501803
|
entity |
| Predicate | hasMainThemes |
P7671
|
FINISHED |
| Object | magic |
—
|
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: magic | Statement: [Legends of Shannara, hasMainThemes, magic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainThemes Context triple: [Legends of Shannara, hasMainThemes, magic]
-
A.
hasCentralTheme
Indicates that one entity serves as the primary or dominant theme or subject matter of another entity.
-
B.
hasMainThemeCharacter
Indicates that a work (such as a story, film, or game) features a specific character as its central or primary thematic focus.
-
C.
hasPersonalThemes
Indicates that something (such as a work, message, or expression) involves themes that are personal, intimate, or directly related to an individual’s own experiences or inner life.
-
D.
hasThematicOrigin
Indicates that something originates from, or is thematically derived from, a particular source, subject, or theme.
-
E.
notableTheme
chosen
Indicates that a particular theme is prominently featured in, or strongly associated with, an entity such as a work, event, or body of content.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a1b03c8190984d9db6d3251308 |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:32 a.m.