Triple
T37511251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graviton Surge |
E932521
|
entity |
| Predicate | chargeSource |
P36932
|
FINISHED |
| Object | damage dealt by Zarya |
—
|
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: damage dealt by Zarya | Statement: [Graviton Surge, chargeSource, damage dealt by Zarya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeSource Context triple: [Graviton Surge, chargeSource, damage dealt by Zarya]
-
A.
paymentSource
Indicates the origin or method from which a payment is provided or funded in a transaction.
-
B.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
C.
rechargeSource
chosen
Indicates that one entity serves as the power or energy provider used to recharge another entity.
-
D.
chargedOn
Indicates that a fee, cost, or financial amount is applied to an account, entity, or transaction at a specific time or in connection with a particular event.
-
E.
chargeType
Indicates the category or nature of a charge applied in a transaction or interaction between entities (e.g., fee type, billing classification, or legal charge type).
- 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.