Triple
T37554139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molten Core |
E933653
|
entity |
| Predicate | attunementQuest |
P184907
|
FINISHED |
| Object | Attunement to the Core |
—
|
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: Attunement to the Core | Statement: [Molten Core, attunementQuest, Attunement to the Core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attunementQuest Context triple: [Molten Core, attunementQuest, Attunement to the Core]
-
A.
requiresAttunementOriginal
Indicates that the item or effect necessitates attunement by a creature before its full properties or benefits can be used.
-
B.
centralQuest
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
-
C.
questContent
chosen
Indicates that one entity is the content, objective, or narrative substance of a quest associated with another entity.
-
D.
enchantedTo
Indicates that one entity has been magically imbued or altered so that it possesses a special effect, property, or behavior caused by another entity.
-
E.
objectOfQuest
Indicates that one entity is the target, goal, or item being sought or pursued in another entity’s quest or mission.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.