Triple
T37511252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graviton Surge |
E932521
|
entity |
| Predicate | roleSynergy |
P188185
|
FINISHED |
| Object | strong with burst-damage heroes |
—
|
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: strong with burst-damage heroes | Statement: [Graviton Surge, roleSynergy, strong with burst-damage heroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleSynergy Context triple: [Graviton Surge, roleSynergy, strong with burst-damage heroes]
-
A.
roleOnPern
Indicates the specific function, position, or duty an entity holds within the context of Pern.
-
B.
rolePurpose
Indicates the intended function, objective, or responsibility that a given role is meant to fulfill.
-
C.
roleInTheWay
Indicates that one entity is obstructing, hindering, or otherwise blocking another entity’s progress, action, or intended path.
-
D.
roleOfGroup
Indicates the function, responsibility, or position that a group holds within a broader context or structure.
-
E.
roleWith
Indicates that one entity holds or performs a particular role in relation to another entity.
- 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_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.