Triple
T11541852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azeroth |
E273692
|
entity |
| Predicate | hasWorldSoul |
P99609
|
FINISHED |
| Object | slumbering titan |
—
|
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: slumbering titan | Statement: [Azeroth, hasWorldSoul, slumbering titan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorldSoul Context triple: [Azeroth, hasWorldSoul, slumbering titan]
-
A.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
B.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
-
C.
hasWorldStructure
Indicates that an entity possesses or is characterized by a particular overall world-level organization, framework, or structural configuration.
-
D.
receivesSoulsOf
Indicates that one entity takes in or accepts the souls of another entity or group of entities.
-
E.
livesInWorldWith
Indicates that one entity exists or resides within the same world or universe as another entity.
- F. None of above. chosen
Provenance (4 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e09eec8190894069d86b79183d |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d8279925e4819089210611c0d8e61a |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:37 p.m.