Triple
T38589984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashkandi, Greatsword of the Brotherhood |
E932430
|
entity |
| Predicate | isPhysicalDamageWeapon |
P191240
|
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: [Ashkandi, Greatsword of the Brotherhood, isPhysicalDamageWeapon, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPhysicalDamageWeapon Context triple: [Ashkandi, Greatsword of the Brotherhood, isPhysicalDamageWeapon, true]
-
A.
isOffensiveWeapon
Indicates that something qualifies as a weapon designed or used to cause harm or injury, typically in an aggressive or unlawful context.
-
B.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
-
C.
weapon
Indicates that one entity is used as a weapon by, or serves as the weapon of, another entity.
-
D.
isStartingWeaponFor
Indicates that a weapon is the initial or default weapon assigned to or used by an entity at the start of a game, scenario, or progression.
-
E.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.