Triple
T37511381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McCree |
E932524
|
entity |
| Predicate | crowdControlAbility |
P30853
|
FINISHED |
| Object | Flashbang |
—
|
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: Flashbang | Statement: [McCree, crowdControlAbility, Flashbang]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crowdControlAbility Context triple: [McCree, crowdControlAbility, Flashbang]
-
A.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
-
B.
effectControlledBy
Indicates that the occurrence, magnitude, or outcome of one effect is regulated, determined, or constrained by another specified factor or agent.
-
C.
passiveAbility
Indicates that an entity possesses an inherent, automatically functioning ability that does not require deliberate activation.
-
D.
canControl
chosen
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
E.
confersResistanceTo
Indicates that one entity provides or imparts resistance or reduced susceptibility to another entity against a specified agent, condition, or effect.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.