Triple
T37470979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonesmith Heirmir |
E931150
|
entity |
| Predicate | playableStatus |
P191134
|
FINISHED |
| Object | non-playable |
—
|
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: non-playable | Statement: [Bonesmith Heirmir, playableStatus, non-playable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableStatus Context triple: [Bonesmith Heirmir, playableStatus, non-playable]
-
A.
playableMode
Indicates that a particular mode, configuration, or state can be actively used or played within a system or application.
-
B.
playable
Indicates that an entity can be used or performed as a game, media, or activity in its intended interactive or functional form.
-
C.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
D.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
E.
playerStatus
Indicates the current state or condition of a player within a game or system, such as their activity, health, or participation status.
- F. None of above. chosen
Provenance (4 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcda35dc048190a3c90e15230900e0 |
completed | May 7, 2026, 6:30 p.m. |
Created at: May 3, 2026, 4:17 p.m.