Triple
T38592408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blink (Overwatch ability) |
E932483
|
entity |
| Predicate | maxCharges |
P98726
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Blink (Overwatch ability), maxCharges, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxCharges Context triple: [Blink (Overwatch ability), maxCharges, 3]
-
A.
numberOfCharges
Indicates the count of distinct charges, accusations, or fee items associated with an entity or event.
-
B.
mainCharge
Indicates that one charge in a set of legal accusations is designated as the primary or most significant offense.
-
C.
maximumUsage
chosen
Indicates the highest allowable or observed amount, frequency, or extent to which something can be used within a defined context or period.
-
D.
canCharge
Indicates that one entity has the ability or permission to charge another entity, typically in the sense of applying a cost, fee, or electrical charge.
-
E.
statutoryLimitPerIncidentUSD
Indicates the maximum monetary amount, in U.S. dollars, that is legally allowed to be claimed or paid for a single incident under a specific statute or regulation.
- 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_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. |
Created at: May 3, 2026, 4:32 p.m.