Triple
T37457356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Hand Recruit |
E930831
|
entity |
| Predicate | canBeBuffedBy |
P198914
|
FINISHED |
| Object | Quartermaster |
—
|
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: Quartermaster | Statement: [Silver Hand Recruit, canBeBuffedBy, Quartermaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeBuffedBy Context triple: [Silver Hand Recruit, canBeBuffedBy, Quartermaster]
-
A.
canBeEnchantedWith
Indicates that an entity is capable of receiving or being affected by a specified enchantment.
-
B.
canBuffCthunOnBattlefield
Indicates that an entity has the ability to increase or enhance C'Thun's stats or effects while C'Thun is currently on the battlefield.
-
C.
canBuffCthunInHand
Indicates that an entity has the ability to increase or enhance C'Thun's stats or effects while C'Thun is still in the player's hand.
-
D.
canSoulbindWith
Indicates that one entity is capable of forming a soulbound or spiritually bound connection with another entity.
-
E.
canBeAwardedTo
Indicates that something is eligible to receive or be granted a particular award, honor, or recognition.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
| PDg | Predicate description generation | batch_69ff136c68b481909b83d5b8a3693622 |
completed | May 9, 2026, 10:58 a.m. |
Created at: May 3, 2026, 4:17 p.m.