Triple
T20983388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kindred |
E516824
|
entity |
| Predicate | strategyUse |
P118338
|
FINISHED |
| Object | Commonly used in solo queue to compensate for lack of voice chat |
—
|
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: Commonly used in solo queue to compensate for lack of voice chat | Statement: [Kindred, strategyUse, Commonly used in solo queue to compensate for lack of voice chat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategyUse Context triple: [Kindred, strategyUse, Commonly used in solo queue to compensate for lack of voice chat]
-
A.
strategyType
Indicates the specific kind or category of strategy associated with an entity or action.
-
B.
strategyComponent
Indicates that one element functions as a constituent or building block within a broader strategy.
-
C.
strategyNote
chosen
Indicates that an entity is associated with a note or annotation describing a strategy, plan, or tactical approach related to it.
-
D.
strategizesFor
Indicates that one entity plans or devises strategies on behalf of, or in support of, another entity.
-
E.
strategyEmphasis
Indicates an entity’s primary focus or priority within a broader strategy or plan.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe03244819097630333e70c4e88 |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.