Triple
T35011420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orsimer |
E1009946
|
entity |
| Predicate | typicalSkillBonus |
P206800
|
FINISHED |
| Object | two-handed weapons (varies by game) |
—
|
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: two-handed weapons (varies by game) | Statement: [Orsimer, typicalSkillBonus, two-handed weapons (varies by game)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSkillBonus Context triple: [Orsimer, typicalSkillBonus, two-handed weapons (varies by game)]
-
A.
skillType
Indicates the specific category or kind of skill that characterizes or classifies an associated skill-related entity or action.
-
B.
perkType
Indicates the specific category or kind of benefit, bonus, or advantage associated with an entity or situation.
-
C.
damageBonus
Indicates that an entity receives an additional amount of damage dealt beyond its base damage value.
-
D.
killsAt
Indicates that one entity causes the death of another entity at a specific time or event.
-
E.
skillFactor
Indicates the degree or level of skill associated with an entity in performing a particular task or activity.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.