Triple
T38583668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azerite |
E932298
|
entity |
| Predicate | discoveredAfter |
P70812
|
FINISHED |
| Object | defeat of the Burning Legion |
—
|
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: defeat of the Burning Legion | Statement: [Azerite, discoveredAfter, defeat of the Burning Legion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredAfter Context triple: [Azerite, discoveredAfter, defeat of the Burning Legion]
-
A.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with another entity.
-
B.
remainsDiscoveredOn
Indicates that the physical remains of an entity were found or uncovered at a particular location or site.
-
C.
coveredSince
Indicates that one entity has been under the protection, applicability, or effect of another entity continuously starting from a specified point in time.
-
D.
wasDiscoveredSoonAfter
chosen
Indicates that one event, object, or fact was discovered a relatively short time after another specified reference point or event.
-
E.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:32 p.m.