Triple
T37541699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Warcraft patch 9.0.1 |
E933339
|
entity |
| Predicate | gameVersionMajor |
P10600
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [World of Warcraft patch 9.0.1, gameVersionMajor, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameVersionMajor Context triple: [World of Warcraft patch 9.0.1, gameVersionMajor, 9]
-
A.
majorVersion
chosen
Indicates that one entity specifies or corresponds to the primary (major) version number of another entity in a versioning scheme.
-
B.
latestMajorVersionNumber
Indicates the relationship that specifies the most recent major version number associated with an entity.
-
C.
currentMajorVersionFrom
Indicates that one entity derives or identifies the current major version number from another entity.
-
D.
latestMajorVersionFamily
Indicates that one entity is the most recent major version within a defined version family or series relative to another entity.
-
E.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
- 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_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.