Triple
T9477241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shell Toss |
E228545
|
entity |
| Predicate | canBeBoostedBy |
P79242
|
FINISHED |
| Object | attack-boosting effects |
—
|
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: attack-boosting effects | Statement: [Shell Toss, canBeBoostedBy, attack-boosting effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeBoostedBy Context triple: [Shell Toss, canBeBoostedBy, attack-boosting effects]
-
A.
allowsBoosters
chosen
Indicates that one entity permits the use, presence, or activation of boosters in relation to another entity or context.
-
B.
canBeEarnedBy
Indicates that something (such as a reward, status, or resource) is obtainable through the actions, efforts, or qualifications of a particular entity.
-
C.
boosterType
Indicates the specific kind or category of booster associated with an entity or action.
-
D.
reboostCapability
Indicates the ability of one entity to provide thrust or propulsion to raise or adjust the orbit of another entity.
-
E.
canBeAwarded
Indicates that an entity is eligible to receive or be granted a particular award, prize, or honor.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd801386948190890133f622ff360b |
completed | April 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.