Triple
T37470682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kleia |
E931143
|
entity |
| Predicate | firstIntroducedInPatch |
P99620
|
FINISHED |
| Object | Shadowlands pre-patch 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: Shadowlands pre-patch era | Statement: [Kleia, firstIntroducedInPatch, Shadowlands pre-patch era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIntroducedInPatch Context triple: [Kleia, firstIntroducedInPatch, Shadowlands pre-patch era]
-
A.
introducedInPatch
chosen
Indicates that something (such as a feature, change, or fix) first appeared or became available in a specific software patch.
-
B.
reintroducedInPatch
Indicates that something previously removed or absent was added back or made available again as part of a specific software patch or update.
-
C.
introducedInGameAs
Indicates that an entity first appeared or was made available within a specific game title.
-
D.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
E.
introducedInExpansion
Indicates that something (such as a feature, item, or concept) was first added or made available as part of a specific expansion.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.