Triple
T37511480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symmetra |
E932526
|
entity |
| Predicate | abilityTheme |
P189048
|
FINISHED |
| Object | hard-light constructs |
—
|
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: hard-light constructs | Statement: [Symmetra, abilityTheme, hard-light constructs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abilityTheme Context triple: [Symmetra, abilityTheme, hard-light constructs]
-
A.
usesThemeBy
Indicates that one entity incorporates, applies, or is based on a theme that was created, defined, or provided by another entity.
-
B.
shapeTheme
Indicates a relationship where one entity’s form, outline, or geometric characteristics serve as a central motif or organizing principle for another entity.
-
C.
isThemedTo
Indicates that one entity is designed, styled, or conceptually based around the subject, motif, or theme represented by another entity.
-
D.
themeChange
Indicates that an entity undergoes a change in its theme, style, or subject, typically transitioning from one thematic state or configuration to another.
-
E.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
| PDg | Predicate description generation | batch_69fbb083ab708190a18b045311106f27 |
completed | May 6, 2026, 9:20 p.m. |
Created at: May 3, 2026, 4:17 p.m.