Triple
T11543049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercy |
E273718
|
entity |
| Predicate | secondaryFunctionInGame |
P2114
|
FINISHED |
| Object | damage boosting 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: damage boosting allies | Statement: [Mercy, secondaryFunctionInGame, damage boosting allies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryFunctionInGame Context triple: [Mercy, secondaryFunctionInGame, damage boosting allies]
-
A.
secondaryFunction
chosen
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
B.
secondaryActivity
Indicates that an entity engages in an additional, non-primary activity or role alongside its main activity.
-
C.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
D.
secondarySetting
Indicates that an entity serves as an additional or supporting setting context for another entity, rather than being the primary setting.
-
E.
secondaryProtagonistType
Indicates the role or category of a work’s secondary main character in relation to the primary protagonist.
- 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_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. |
Created at: April 8, 2026, 9:37 p.m.