Triple
T38593246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tactical Visor |
E932501
|
entity |
| Predicate | ultimateChargeSource |
P191264
|
FINISHED |
| Object | Damage dealt |
—
|
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 | Statement: [Tactical Visor, ultimateChargeSource, Damage dealt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimateChargeSource Context triple: [Tactical Visor, ultimateChargeSource, Damage dealt]
-
A.
rechargeSource
Indicates that one entity serves as the power or energy provider used to recharge another entity.
-
B.
hasRechargeSource
Indicates that an entity receives or can obtain electrical power or energy from a specified source for recharging.
-
C.
rechargedBy
Indicates that one entity restores or replenishes the energy, power, or charge of another entity.
-
D.
mainCharge
Indicates that one charge in a set of legal accusations is designated as the primary or most significant offense.
-
E.
ultimateSource
Indicates that one entity is the original, foundational origin from which another entity ultimately derives.
- F. None of above. chosen
Provenance (4 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_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.