Triple
T37541701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Warcraft patch 9.0.1 |
E933339
|
entity |
| Predicate | gameVersionPatch |
P188176
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [World of Warcraft patch 9.0.1, gameVersionPatch, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameVersionPatch Context triple: [World of Warcraft patch 9.0.1, gameVersionPatch, 1]
-
A.
patchNumber
chosen
Indicates the specific patch or incremental update identifier associated with a software version or release.
-
B.
introducedInPatch
Indicates that something (such as a feature, change, or fix) first appeared or became available in a specific software patch.
-
C.
puncturedVersion
Indicates that one entity is a modified or altered version of another, specifically created by introducing a puncture or hole.
-
D.
liveVersionReleasedOn
Indicates the date or time when a live version of something (such as a product, feature, or content) is officially released or made available.
-
E.
latestMinorVersion
Indicates that one version is the most recent minor (non-major) update within the series of versions derived from another version.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.