Triple
T37511174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fusion Cannons |
E932519
|
entity |
| Predicate | firingOrigin |
P74643
|
FINISHED |
| Object | D.Va’s mech |
—
|
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: D.Va’s mech | Statement: [Fusion Cannons, firingOrigin, D.Va’s mech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firingOrigin Context triple: [Fusion Cannons, firingOrigin, D.Va’s mech]
-
A.
firing
Indicates initiating the discharge of a weapon or explosive device toward a target.
-
B.
firedBy
Indicates that one entity has dismissed or terminated another entity from a position, role, or employment.
-
C.
firingDetail
Indicates that one entity performs or is involved in a specific act of firing (such as discharging a weapon or initiating a shot) toward or in relation to another entity, including contextual details of that firing event.
-
D.
firingPurpose
Indicates the reason or intended objective behind initiating a firing or discharge action.
-
E.
firingPlatform
chosen
Indicates a platform or structure from which a weapon or projectile is launched or fired.
- 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.