Triple
T11547447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Maw |
E273806
|
entity |
| Predicate | patchIntroduced |
P513
|
FINISHED |
| Object | World of Warcraft patch 9.0.1 era |
—
|
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: World of Warcraft patch 9.0.1 era | Statement: [The Maw, patchIntroduced, World of Warcraft patch 9.0.1 era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patchIntroduced Context triple: [The Maw, patchIntroduced, World of Warcraft patch 9.0.1 era]
-
A.
policyIntroduced
Indicates that a specific policy has been formally brought into effect or announced by an authority or organization.
-
B.
introduced
chosen
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
D.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
E.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e3ad548190b2c88332f5d919bd |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.