Triple
T11563751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sombra |
E274202
|
entity |
| Predicate | canReveal |
P9982
|
FINISHED |
| Object | low-health enemies |
—
|
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: low-health enemies | Statement: [Sombra, canReveal, low-health enemies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canReveal Context triple: [Sombra, canReveal, low-health enemies]
-
A.
isRevealedTo
Indicates that previously hidden or unknown information becomes known to a specific entity or group.
-
B.
isRevealedIn
Indicates that something becomes known, disclosed, or made apparent within a particular context, medium, or situation.
-
C.
canExhibit
chosen
Indicates that one entity has the ability or potential to display, manifest, or show a particular property, behavior, or characteristic.
-
D.
hasModeOfRevelation
Indicates the manner or channel through which something is revealed, communicated, or made known.
-
E.
revealedBefore
Indicates that one entity becomes known, disclosed, or made apparent earlier in time than another entity.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd321f88190a57ecaf079fbbc3f |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:37 p.m.