Triple
T37463217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Razorpetal Lasher |
E930969
|
entity |
| Predicate | addedInPatch |
P99620
|
FINISHED |
| Object | 8.0.0 (Journey to Un'Goro release patch) |
—
|
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: 8.0.0 (Journey to Un'Goro release patch) | Statement: [Razorpetal Lasher, addedInPatch, 8.0.0 (Journey to Un'Goro release patch)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedInPatch Context triple: [Razorpetal Lasher, addedInPatch, 8.0.0 (Journey to Un'Goro release patch)]
-
A.
introducedInPatch
chosen
Indicates that something (such as a feature, change, or fix) first appeared or became available in a specific software patch.
-
B.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
C.
addedTo
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
D.
featureAdded
Indicates that a new feature has been introduced or incorporated into a system, product, or entity.
-
E.
patchAvailable
Indicates that an update or fix has been released and is available to be applied to the referenced software or system.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.