Triple
T37458218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Thunder King |
E930851
|
entity |
| Predicate | isCosmeticOnly |
P8752
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Thunder King, isCosmeticOnly, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCosmeticOnly Context triple: [The Thunder King, isCosmeticOnly, true]
-
A.
hasCosmetics
Indicates that one entity possesses, uses, or is associated with cosmetic products or beauty-related items in relation to another entity or context.
-
B.
includesCosmetics
Indicates that one entity contains or encompasses cosmetic products or items as part of its contents or offerings.
-
C.
isCombatOnlyDecoration
Indicates that the object serves purely decorative purposes and is only visible or relevant during combat, without affecting gameplay outside combat.
-
D.
isWearableDecoration
chosen
Indicates that one entity serves as a decorative item intended to be worn on the body by another entity.
-
E.
isTradeOnly
Indicates that the item or entity can only be obtained, exchanged, or interacted with through trading and not by other means such as purchase, crafting, or direct acquisition.
- 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_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.