Triple
T38593485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angelic Descent |
E932506
|
entity |
| Predicate | teamImpact |
P118563
|
FINISHED |
| Object | helps Mercy maintain line of sight to allies |
—
|
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: helps Mercy maintain line of sight to allies | Statement: [Angelic Descent, teamImpact, helps Mercy maintain line of sight to allies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamImpact Context triple: [Angelic Descent, teamImpact, helps Mercy maintain line of sight to allies]
-
A.
impactOnField
Indicates the effect or influence that one entity, action, or development has on a particular field or domain.
-
B.
boardImpact
Indicates the effect or influence that a board (such as a board of directors or governing board) has on outcomes, decisions, or performance.
-
C.
gameplayImpact
chosen
Indicates how one element in a game affects the mechanics, difficulty, or overall experience of playing that game.
-
D.
impactOnStandings
Indicates how an event or outcome affects the relative rankings or standings within a competition or system.
-
E.
seasonImpact
Indicates how a particular season influences or affects another entity, condition, or outcome.
- 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_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. |
Created at: May 3, 2026, 4:32 p.m.