Triple
T37455767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destroyer |
E930794
|
entity |
| Predicate | isOneOfPlayableClasses |
P88329
|
FINISHED |
| Object | three main classes in Torchlight |
—
|
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: three main classes in Torchlight | Statement: [Destroyer, isOneOfPlayableClasses, three main classes in Torchlight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOneOfPlayableClasses Context triple: [Destroyer, isOneOfPlayableClasses, three main classes in Torchlight]
-
A.
hasPlayableCharacter
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
B.
hasProtagonistClass
Indicates that a work’s main character belongs to a specified class or category.
-
C.
hasChampionClass
Indicates that an entity is associated with, or belongs to, a particular champion class or category.
-
D.
isPlayableAllyOf
Indicates that one entity can be used or controlled as an ally in conjunction with another entity, typically within a game or interactive context.
-
E.
playableInGame
chosen
Indicates that something can be used or controlled as an active element within a particular game.
- 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_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.