Triple
T11543145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanzo |
E273720
|
entity |
| Predicate | headshotCapability |
P99958
|
FINISHED |
| Object | Can deal critical damage with headshots |
—
|
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: Can deal critical damage with headshots | Statement: [Hanzo, headshotCapability, Can deal critical damage with headshots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headshotCapability Context triple: [Hanzo, headshotCapability, Can deal critical damage with headshots]
-
A.
portraitOn
Indicates that one entity is depicted as a portrait on the surface or medium of another entity.
-
B.
hasPhotoOn
Indicates that one entity has an associated photograph stored, displayed, or linked on another entity (such as a platform, page, or medium).
-
C.
avatar
Indicates that one entity serves as a representation, embodiment, or proxy of another entity, often in a different form or medium.
-
D.
hasPhotograph
Indicates that one entity possesses, includes, or is associated with a photograph depicting or representing another entity.
-
E.
selfImage
Indicates an entity’s perception, evaluation, or mental representation of itself.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e09eec8190894069d86b79183d |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:37 p.m.