Triple
T37552163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormheim |
E933612
|
entity |
| Predicate | artifactRelated |
P188266
|
FINISHED |
| Object | Aegis of Aggramar |
—
|
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: Aegis of Aggramar | Statement: [Stormheim, artifactRelated, Aegis of Aggramar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artifactRelated Context triple: [Stormheim, artifactRelated, Aegis of Aggramar]
-
A.
artifact
Indicates that one entity is an artifact created, modified, or used by another entity.
-
B.
artifactType
Indicates the specific kind or category of artifact that an entity is classified as.
-
C.
relatedArtifactType
Indicates the specific kind of relationship or linkage that one artifact has to another artifact (e.g., predecessor, successor, reference, dependency).
-
D.
associatedWithWorkOfArt
Indicates a relationship in which an entity is connected or related to a specific work of art, such as through creation, contribution, ownership, or contextual association.
-
E.
associatedItem
Indicates that one item is linked or connected to another in a relevant or context-dependent way, without specifying a more precise relationship.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.