Triple
T38593830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonstrike |
E932515
|
entity |
| Predicate | canBeComboedWith |
P142693
|
FINISHED |
| Object | Graviton Surge |
—
|
NE NERFINISHED |
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: Graviton Surge | Statement: [Dragonstrike, canBeComboedWith, Graviton Surge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeComboedWith Context triple: [Dragonstrike, canBeComboedWith, Graviton Surge]
-
A.
isConsideredCombinationOf
Indicates that something is regarded as being formed by or equivalent to a specific combination of other things or components.
-
B.
designedToCombine
Indicates that one entity is intentionally created or configured to be merged, integrated, or used together with another entity.
-
C.
allowsCombination
Indicates that one entity permits or supports being combined or used together with another entity.
-
D.
hasComb
Indicates that an entity possesses or is equipped with a comb.
-
E.
canBeAddedTo
chosen
Indicates that one entity is capable of being combined or incorporated with another entity, typically without conflict or incompatibility.
- 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_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: May 3, 2026, 4:32 p.m.